Health data you can trust — Technical https://thesis.uya.no/proposals/can-you-trust-this-number/#technical-track BACHELOR Final result: A working data-quality viewer, tests and user instructions. Task: Import two health-record CSVs and flag duplicate IDs, invalid units, missing times, conflicting values and stale values using fixed rules. Data: 50 fictional patients in two CSV files (planned) 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. Requires: Recruit students; use fictional records only. Method: Test against the independent defect key; observe 4 students reconciling records. STEPS Build and test 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. MASTER Final result: Record viewer, test data and error-detection report. 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. STEPS Design, build and test (DSR) 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. CURRENT PROJECT LITERATURE Electronic health record data quality assessment and tools: a systematic review (2023, peer-reviewed): https://pmc.ncbi.nlm.nih.gov/articles/PMC10531113/ Establishes current EHR quality dimensions, methods and the need for task-dependent assessment. Common data quality elements for health information systems: a systematic review (2024, peer-reviewed): https://doi.org/10.1186/s12911-024-02644-7 Consolidates accuracy, consistency, timeliness, completeness, accessibility and understandability. IS THEORY STARTING POINTS Wang & Strong (1996) — Beyond Accuracy: https://www.tandfonline.com/doi/abs/10.1080/07421222.1996.11518099 Distinguish accuracy, completeness, representation and fitness for the task. Vessey & Galletta (1991) — Cognitive Fit: https://pubsonline.informs.org/doi/10.1287/isre.2.1.63 Test whether a representation helps one kind of task more than another. 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. PILOT QUESTION Do source and quality labels help users identify faults in merged health records? EXAMPLE TOOLS Python, pandas, Streamlit Equivalent tools are fine. FIRST 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. LITERATURE SEARCH health records data provenance information quality trust DATA 50 fictional patients in two CSV files (planned) 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. HOW TO TEST IT 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. FINAL RESULT Record viewer, test data and error-detection report. ACCESS OR PEOPLE Recruit 8 students; use fictional records only. TEMPLATES https://thesis.uya.no/starters/can-you-trust-this-number/technical/data-plan.csv https://thesis.uya.no/starters/can-you-trust-this-number/technical/evaluation.csv https://thesis.uya.no/starters/can-you-trust-this-number/technical/literature-matrix.csv Use participant codes instead of names or email addresses.