** About MR-COVID-19 **

  1. Health Track

  2. Quite frankly, our inspiration came from living through a global pandemic. D’Mya pitched the idea to the group after being routinely tested for COVID-19. She noticed during her healthcare administration internship that the Quality Improvement department struggled to keep up with data entry and reporting, despite having robust EHR software. She noticed that one problem with the current EHR system was that it was also expected to manage average day-to-day healthcare needs during a not-so-average global event.

  3. In the last 30 hours, we created a desktop application called M.R. (Medical Reporting, or Miss Rona) COVID-19, in order to streamline the manual reporting practices used by healthcare facilities and testing sites in the U.S. today. Our application will help healthcare workers keep their central EHR separated from confusion and overlap with their COVID reporting. MRCOVID-19 is for use by healthcare professionals to record patient health information, COVID test results, and automatically communicate results to patients via email as they are updated in the system. These results are then used by the healthcare facility to generate positivity and demographic reports for their own records and to report to the state. Current demographic outputs (for Daily, Weekly, Monthly and Yearly data) include: Positive/Negative cases compared to patient symptoms, Cumulative number of infections by Age group, Repartition of positive cases in the US. Extra graphs include: Number of tests conducted by Ethnicity.

  4. To build the application, we used the programming language that most members of our team were familiar with: Java. In order to make the UI more appealing than the included Java GUI library options, we took a risk and implemented JavaFX, a powerful library for UI development that allows for greater flexibility. To design the layout of the final application, we used FXML, which is a markup language that defines the location of buttons, text boxes, etc. within the application frame. This proved to be a powerful tool because we were able to use SceneBuilder to create scenes without writing code. Data visualisation scripts were written in R code, but formatted in .Rhtml to help with embedding.

  5. With such a beginner team, intense time pressure, and a challenging end-goal, difficulties abounded during the hackathon. In order to be as productive as possible, we created a Git repository that was accessible to everyone on the team. Once that was set up, multiple members could design different pages (such as a loading screen or new patient creation page) simultaneously. The largest headache of the project was getting JavaFX to work on all of the member’s computers due to the necessary software downloads and file path juggling.

  6. We are very proud to have accomplished this despite time zone differences in a highly demanding time frame in order to help take some weight off the shoulders of the healthcare workers who need it most. Many team members were also first-time hackers, so we are proud to have created such a successful product.

  7. We learned a plethora of things along the way, spanning from new Java software development platforms, to GitHub collaboration, to learning how to be resourceful in our individual methods of problem-solving in order to accomplish a common goal. If all of our busy schedules allow, we would consider making our solution more robust and taking the idea to market in the future, as we believe that there is a real-world demand for our technology.

Built With

Share this project:

Updates