Selected project 02Python · Tkinter · CSV
A structured patient-record workflow
A desktop application built around the part of healthcare data that never shows up in a dashboard: who is allowed to touch a record, what a valid record looks like, and what gets written down afterwards.
- Discipline
- Healthcare informatics
- Stack
- Python · Tkinter
- Storage
- CSV
- Context
- Academic project
The question
A patient record is only as trustworthy as the process around it. How do you build a small system where access is controlled, entries are checked before they are saved, and every action leaves a trace?
The project
This Python and Tkinter application handles patient-record operations behind a login. Different roles see different capabilities, fields are validated before a record is written, and usage is logged so activity can be reviewed afterwards. Records persist to CSV.
Authenticate the user, validate the record, log the activity.
Three layers
- Access. Role-based login gates which record operations a user can reach.
- Validation. Fields are checked on entry, so malformed records never reach storage.
- Logging. Actions are written to an activity log, which makes the work reviewable after the fact.
Those three concerns are the same ones I meet in practice: in pharmacy systems, in claims work, and in anything that touches protected health information. Building them at small scale made the reasoning behind them concrete.
Skills represented
- Python application structure
- Role-based access design
- Input validation and data integrity
- Activity logging and auditability
- Tkinter interface construction
This overview is based on the project described in my resume. The visual above is a generated portfolio graphic rendered in the browser. It illustrates record relationships and does not display real patient data.
Visit my GitHub