Follow-up after digital consultations
Turn consultation notes into confirmed follow-up tasks with an owner and due date.
Technical
Bachelor’s · applied project
Final result
A working follow-up checklist with tested validation rules.
Material to create
30 fictional consultation notes
Write 150–250 words per note with 0–4 actions. Label action, owner and deadline separately; include 10 notes with missing owners or dates.
What to do
- Build a structured follow-up form that links actions to their source note.
How it is tested
Enter actions manually from the fictional notes; check missing-owner/date handling and observe 4 task sessions.
Before you start
Example tools · Qwen2.5-7B-Instruct, Python, Streamlit These are suggestions; equivalent tools are fine.
Access or people · Clinical review of scripts; recruit students. No patient notes.
Research method · Build and test · 6 steps
- Read the starting sources and choose one established implementation method.
- Write the requirements, data fields, system diagram and test cases.
- Prepare 30 fictional consultation notes. Make the answer key and pass criteria before testing.
- Build a working version of a working follow-up checklist with tested validation rules.
- Run function, integration and failure-case tests. Record each result.
- Run the practical evaluation and list the changes the system still needs.
Download the complete bachelor plan
Download bachelor instructionsMaster’s · research project
Final result
Pinned extraction pipeline, confirmation interface, labelled notes and four-way evaluation.
Material to create
30 fictional consultation notes
Write 150–250 words per note with 0–4 actions. Label action, owner and deadline separately; include 10 notes with missing owners or dates.
What to do
- Validate pinned Qwen output through a Pydantic schema for action span, source span, owner, due date, unknown reason and status; count parse failure as failure.
- Compare keyword/date rules, raw LLM, manual extraction and LLM-plus-confirmation on scenario-family splits with an independently reviewed key.
- Report action-span precision/recall/F1, conditional owner/date accuracy, invented responsibility, residual confirmation errors, introduced errors, source use and time.
How it is tested
On 20 held-out notes compare keyword/date rules, raw Qwen, manual structured extraction and Qwen plus human confirmation. Report action-span precision/recall/F1, owner/date accuracy conditional on matched actions, invented responsibility, residual post-confirmation errors, corrections introduced, source use and time.
Before you start
Example tools · Qwen2.5-7B-Instruct, Python, Streamlit These are suggestions; equivalent tools are fine.
Access or people · Clinical review of scripts; recruit students. No patient notes.
Start with these three actions
- Write 3 fictional notes and manually label every action, including explicit missing values. Confirm access to inference compute and record model, software and hardware versions.
- Create the development/held-out split before trying prompts. Keep held-out results hidden until tuning is complete.
- Pilot action confirmation on 3 development notes and fix the scoring rules.
Files, questions and sources
Pilot question: Does source-linked task confirmation reduce missed or incorrectly assigned follow-up actions?
Literature search: clinical consultation follow up task extraction accountability
Empty CSV templates: data-plan.csv · evaluation.csv · literature-matrix.csv
Download starter instructionsResearch method · Design, build and test (DSR) · 7 steps
- Read the newest papers and list the closest existing systems.
- Write down the versions, fields, data split, case assignment, random seeds and correct answers for 30 fictional consultation notes.
- Draw the user workflow, data model and system architecture. List the requirements and pass criteria.
- Build a working version of pinned extraction pipeline, confirmation interface, labelled notes and four-way evaluation.
- Test every function, connection and failure case. Save the failed tests as well as the passed tests.
- Compare the system with the named alternative. Then run the user task or decision task in the assignment.
- Report the measured result, the failed cases and the design lessons another team can reuse.
Research question and sources
Research question: Study whether confirmation reduces extraction errors without creating false responsibility. Compare keyword/date rules, raw Qwen, manual extraction and Qwen plus confirmation; analyse missing owners and dates separately.
Research result: Evidence about how confirmation changes accuracy and accountability in follow-up work.
Current project literature
- Evaluating Large Language Models in extracting cognitive exam dates and scores (2024) peer-reviewed
Provides a recent expert-reviewed clinical information-extraction design and error analysis. - Systematic Evaluation of Large Language Models for Post-Discharge Clinical Action Extraction (2026) preprint
Directly studies the emerging task of extracting safety-critical follow-up actions from notes.
IS theory starting points
- Amershi et al. (2019) — Guidelines for Human-AI Interaction — Select and justify the correction, explanation or uncertainty design being tested.
- Buçinca et al. (2021) — To Trust or to Think — Derive a competing explanation based on verification effort and overreliance.
Search Scopus or Web of Science and ACM Digital Library using the topic query, then follow citations to the thesis start date. Record searches and compare methods, data, findings and limitations in literature-matrix.csv. Use that review to confirm or revise the gap and choose a current comparator. The linked papers are starting points.
Search terms: clinical consultation follow up task extraction accountability
Non-technical
Bachelor’s · applied project
Final result
A revised handover checklist and workflow map.
Material to create
12 scripted handovers
Create 4 clear cases, 4 with missing owners and 4 with missing deadlines. Record intended actions separately.
What to do
- Find where follow-up actions lose their owner or deadline.
How it is tested
Use paper handovers in 4 staff walkthroughs; describe missing information and responsibility hand-offs.
Before you start
Example tools · LibreOffice Writer/Calc, audio recorder with consent; no programming required. These are suggestions; equivalent tools are fine.
Access or people · Recruit health professionals and review the fictional cases.
Research method · Study and improve · 6 steps
- Read the starting sources and write the exact information problem.
- Prepare 12 scripted handovers and a separate answer sheet or coding sheet.
- Run one pilot and fix unclear questions.
- Collect the named evidence with consent.
- Group the findings with the stated categories and check the answer sheet.
- Produce a revised handover checklist and workflow map. List the three most useful changes.
Download the complete bachelor plan
Download bachelor instructionsMaster’s · research project
Final result
Handover checklist and documented causes of missed follow-up.
Material to create
12 scripted handovers + 8 staff interviews
Create 4 clear cases, 4 with missing owners and 4 with missing deadlines. Record intended actions separately.
What to do
- Prepare paper consultation notes and follow-up lists.
- Ask staff to assign responsibility and identify actions at risk of being missed.
How it is tested
Think-aloud review; count missed actions and code responsibility disputes and handover failures.
Before you start
Example tools · LibreOffice Writer/Calc, audio recorder with consent; no programming required. These are suggestions; equivalent tools are fine.
Access or people · Recruit health professionals and review the fictional cases.
Start with these three actions
- Prepare a pilot with 2 examples from: 12 scripted handovers + 8 staff interviews. Write the task questions and a reference answer sheet.
- Write a recruitment message, information sheet and consent form for the participants named above. Agree privacy handling with the supervisor before contact.
- Pilot one session after approval; revise unclear questions, finalise the task sets and coding categories, then recruit the planned sample.
Files, questions and sources
Pilot question: Which handover details leave staff uncertain about follow-up responsibility?
Literature search: clinical consultation follow up task extraction accountability qualitative scenario study
Interview prompts
- What actions must happen next and who owns them?
- Which action is most likely to be missed?
- What would confirm that the handover is complete?
Empty CSV templates: study-plan.csv · coding-sheet.csv · literature-matrix.csv
Download starter instructionsResearch method · Study, compare and explain · 7 steps
- Read the newest papers and write one exact research question.
- State which people, cases or documents you will study and what you will compare.
- Write the selection rules, questions and analysis steps for 12 scripted handovers + 8 staff interviews.
- Run one pilot. Fix unclear questions or categories, then keep the guide unchanged.
- Collect the named interviews, cases or documents with consent.
- Analyse them with the stated comparison or coding method. Keep disagreements and missing data.
- Report the answer, the evidence and the practical output named in the assignment.
Research question and sources
Research question: Explain why action tables resolve some handover failures but leave others untouched. Contrast information-format problems with disputed responsibility using matched narrative/table cases.
Research result: An explanatory model separating representation failures from ownership failures.
Current project literature
- Evaluating Large Language Models in extracting cognitive exam dates and scores (2024) peer-reviewed
Provides a recent expert-reviewed clinical information-extraction design and error analysis. - Systematic Evaluation of Large Language Models for Post-Discharge Clinical Action Extraction (2026) preprint
Directly studies the emerging task of extracting safety-critical follow-up actions from notes.
IS theory starting points
- Vessey & Galletta (1991) — Cognitive Fit — Test whether a representation helps one kind of task more than another.
- Orlikowski & Gash (1994) — Technological Frames — Compare how roles interpret the purpose, operation and use of the same system.
Search Scopus or Web of Science and ACM Digital Library using the topic query, then follow citations to the thesis start date. Record searches and compare methods, data, findings and limitations in literature-matrix.csv. Use that review to confirm or revise the gap and choose a current comparator. The linked papers are starting points.
Search terms: clinical consultation follow up task extraction accountability qualitative scenario study
Your degree, track and shortlist are saved in this browser.