-
Login Page - Requires correct info, uploads the SQL data.
-
Addition, Update, Delete Features - Allows user to add, update, delete.
-
Audit Log - Stores any edits to the data.
-
Strict Search - Search based off one variable.
-
Range Search - Search based off multiple variables, with conditions.
-
Check Data - Prints subjects holding outlier data.
Inspiration
The inspiration behind HealthData Tracker was to create a robust system for managing medical data, allowing users to easily update, delete, and perform range searches on health-related information. We figured out that communication in the medical workspace is one of the biggest problems which leads to deaths.
What it does
HealthData Tracker provides a user-friendly interface to interact with a medical database. Users can update existing records, delete entries, and perform range searches based on various parameters such as age, scores, and gender. Our first solution was a password where only certain people can access the tracker. It has an audit log that stores all edits, storing addition, updating, and deletion. We also implemented a button that checks the entire data set and gives a warning if any of the data is more or less than 2 standard deviations from the mean.
How we built it
The application is built using Java, leveraging Swing for the graphical user interface. It utilizes MySQL for database management. We used two referenced libraries to help us achieve this, rs2xml.jar, and MySQL connector. I first made the data in MySQL, and from there we figured out a way to connect that server into Java with that MySQL connector referenced library. From there we used our previous skills of GUI with swing and made our interface work.
Challenges we ran into
One of the significant challenges we encountered was implementing a data validation system. Ensuring data integrity and identifying outliers in medical scores required a lot of checks, and making sure we didn't print out the code address instead of the data. Additionally, creating an effective logging mechanism for tracking user actions presented its own set of challenges, due to the fact it used a .txt file to hold the audit log, and made an .txt file if it was not present.
Accomplishments that we're proud of
We are proud of successfully implementing a data validation system that identifies outliers in medical scores. Achieving this functionality greatly enhanced the reliability for our application. Additionally, we are proud we successfully implemented a comprehensive logging system for user actions contributes to system transparency and accountability.
What we learned
We learned MySQL from scratch and figured out how to upload a .csv file with medical data to sql, and connect it to Java. This was the most important thing we learned during this hackathon, and we learned a lot about the storage of data.
What's next for HealthData Tracker
We had three goals which we weren't able to accomplish during this hackathon.
The first is more passwords for more specificity. For example, a doctor would have a password which would allow him to read/write on this program. However, a nurse would only have a password to read, causing there to be less issues regarding tampering of data.
The second item we couldn't accomplish was multiple tabs of data in the sheets. What we would do is have an upload .csv file, where we would take another sample of data, and then we store that data alongside other samples.
Our third was that we intended to write two documents: a User Document, and a Technical Document. The user document makes it easier for a user to use it, and a technical document is for technicians to fix any problems that occur with the program with ease.
Log in or sign up for Devpost to join the conversation.