← All proposals
Illustration: Healthcare information-system concept: Can you trust this number?

Health data you can trust

Show conflicting values, outdated observations and missing fields when two health records are combined.

Download brief

Technical

Bachelor’s · applied project

Final result

A working data-quality viewer, tests and user instructions.

01

Material to create

50 fictional patients in two CSV files

Create two CSVs with 50 observations each for 50 fictional patients: patient_id, event_id, measurement, value, unit, time and source. Plant 8 duplicate IDs, 8 incompatible measurement–unit pairs, 8 missing timestamps, 8 conflicting values within a fixed time window and 8 stale values beyond a predefined threshold in non-overlapping records; include clean repeats and convertible units.

02

What to do

  • Import two health-record CSVs and flag duplicate IDs, invalid units, missing times, conflicting values and stale values using fixed rules.
03

How it is tested

Test against the independent defect key; observe 4 students reconciling records.

04

Before you start

Example tools · Python, pandas, Streamlit These are suggestions; equivalent tools are fine.

Access or people · Recruit students; use fictional records only.

Research method · Build and test · 6 steps
  1. Read the starting sources and choose one established implementation method.
  2. Write the requirements, data fields, system diagram and test cases.
  3. Prepare 50 fictional patients in two CSV files. Make the answer key and pass criteria before testing.
  4. Build a working version of a working data-quality viewer, tests and user instructions.
  5. Run function, integration and failure-case tests. Record each result.
  6. Run the practical evaluation and list the changes the system still needs.
Download the complete bachelor planDownload bachelor instructions

Master’s · research project

Final result

Record viewer, test data and error-detection report.

01

Material to create

50 fictional patients in two CSV files

Create two CSVs with 50 observations each for 50 fictional patients: patient_id, event_id, measurement, value, unit, time and source. Plant 8 duplicate IDs, 8 incompatible measurement–unit pairs, 8 missing timestamps, 8 conflicting values within a fixed time window and 8 stale values beyond a predefined threshold in non-overlapping records; include clean repeats and convertible units.

02

What to do

  • Build a pandas/Pandera reconciliation pipeline with immutable originals, (patient_id,event_id) identity, a fixed unit dictionary and auditable proposed resolutions.
  • Plant and label duplicates, invalid units, missing times, conflicts and stale values; define conversion, conflict-window and staleness rules before testing.
  • Verify detector precision/recall and false positives by defect type, then measure reconciliation accuracy, false corrections, unresolved faults and time.
03

How it is tested

Verify all 40 planted faults and legitimate controls; report detector precision, recall and false positives by type. Eight advanced health-information students complete 8 non-overlapping reconciliation tasks; report per-person accuracy, false corrections, unresolved faults and time.

04

Before you start

Example tools · Python, pandas, Streamlit These are suggestions; equivalent tools are fine.

Access or people · Recruit 8 students; use fictional records only.

01—03

Start with these three actions

  1. Write 5 fictional patients in both exports; preserve a clean reference copy.
  2. Add one fault of each type and record its expected detection in the answer key.
  3. Test the merge on those records before expanding to all 50 patients.
Files, questions and sources

Pilot question: Do source and quality labels help users identify faults in merged health records?

Literature search: health records data provenance information quality trust

Download starter instructions
Research method · Design, build and test (DSR) · 7 steps
  1. Read the newest papers and list the closest existing systems.
  2. Write down the versions, fields, data split, case assignment, random seeds and correct answers for 50 fictional patients in two CSV files.
  3. Draw the user workflow, data model and system architecture. List the requirements and pass criteria.
  4. Build a working version of record viewer, test data and error-detection report.
  5. Test every function, connection and failure case. Save the failed tests as well as the passed tests.
  6. Compare the system with the named alternative. Then run the user task or decision task in the assignment.
  7. Report the measured result, the failed cases and the design lessons another team can reuse.
Research question and sources

Research question: Investigate whether quality warnings help reconciliation equally for missing, conflicting and duplicate data. Derive separate predictions from data-quality and cognitive-fit research; test them by defect type in the same viewer.

Research result: Design principles relating defect type, provenance warning and novice reconciliation decisions.

Current project literature

IS theory starting points

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: health records data provenance information quality trust

Non-technical

Bachelor’s · applied project

Final result

A record-layout recommendation and data-quality checklist.

01

Material to create

12 fictional merged records

Create 12 paper records: 6 clean controls and 2 each with a unit conflict, missing time or stale value. Prepare source-labelled and source-hidden versions with identical values, units and times; never show the defect key.

02

What to do

  • Identify which record labels users need to resolve conflicting values.
03

How it is tested

Use the paper records in 4 task sessions; describe problems using established data-quality categories.

04

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-information students.

Research method · Study and improve · 6 steps
  1. Read the starting sources and write the exact information problem.
  2. Prepare 12 fictional merged records and a separate answer sheet or coding sheet.
  3. Run one pilot and fix unclear questions.
  4. Collect the named evidence with consent.
  5. Group the findings with the stated categories and check the answer sheet.
  6. Produce a record-layout recommendation and data-quality checklist. List the three most useful changes.
Download the complete bachelor planDownload bachelor instructions

Master’s · research project

Final result

Annotated record examples and findings on trust in data.

01

Material to create

12 fictional merged records + 8 sessions

Create 12 paper records: 6 clean controls and 2 each with a unit conflict, missing time or stale value. Prepare source-labelled and source-hidden versions with identical values, units and times; never show the defect key.

02

What to do

  • Prepare merged records with and without source and quality labels.
  • Ask participants which values they would trust and why.
03

How it is tested

Within-person think-aloud study with balanced order. Count correctly identified faults; code reasons for trusting a value.

04

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 8 health-information students.

01—03

Start with these three actions

  1. Prepare a pilot with 2 examples from: 12 fictional merged records + 8 sessions. Write the task questions and a reference answer sheet.
  2. Write a recruitment message, information sheet and consent form for the participants named above. Agree privacy handling with the supervisor before contact.
  3. 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 record details do users rely on when two sources disagree?

Literature search: health records data provenance information quality trust qualitative scenario study

Interview prompts

  • Which value would you use and which source supports it?
  • Which inconsistency needs clarification?
  • Who should correct the record?
Download starter instructions
Research method · Study, compare and explain · 7 steps
  1. Read the newest papers and write one exact research question.
  2. State which people, cases or documents you will study and what you will compare.
  3. Write the selection rules, questions and analysis steps for 12 fictional merged records + 8 sessions.
  4. Run one pilot. Fix unclear questions or categories, then keep the guide unchanged.
  5. Collect the named interviews, cases or documents with consent.
  6. Analyse them with the stated comparison or coding method. Keep disagreements and missing data.
  7. Report the answer, the evidence and the practical output named in the assignment.
Research question and sources

Research question: Explain when provenance changes trust and when task-relevant completeness matters more. Compare matched records using data-quality dimensions; examine contradictory trust/verification decisions.

Research result: A refined explanation of how users judge record fitness for a task.

Current project literature

IS theory starting points

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: health records data provenance information quality trust qualitative scenario study

Your degree, track and shortlist are saved in this browser.