Although health sector is traditionally a conservative and slow-adapting industry, there is an increasing volume of new tools providing new alternatives to provide medical care to patients in very innovative ways, such as web platforms where video-on-demand VisitForm can be made with a variety of physicians, therapists, specialists and health professionals in general. For instance, websites like amwell.com or livehealthonline.com.
However, if these types of tools serve as an excellent way to provide wider access to medical care, sometimes we would like to know what happens next ... after the visit is over.
Currently, the industry, in general, does not track whether medical procedures or diagnoses work or not, and frequently patients don't monitor their health after a treatment as seriously as they should. According to studies, doctors have a hard time finding any data exploring the long-term effects of procedures and treatements, because 84 percent of U.S.-recognized medical specialties have no data registries at all.
I would like to build a platform that allows for better control of medical treatments after the visit by tracking the progress of patients, giving them a way to evaluate the outcome of treatment and for physicians a tool to measure their effectiveness in their diagnoses and prescriptions.
- Security/Authentication
- Tomcat's JDBC Realm Authentication
- Patient role: create/read/update (cru) their own profiles, visits and treatments, in general any data they have entered previously.
- Provider role: create/read/update (cru) their own profiles, diagnostics, visits and treatments, in general any data they have entered previously.
- All: anyone can view information pages (no login)
- Database
- MySQL
- Store patients and providers
- Store all data of VisitForm and treatments
- ORM Framework
- Hibernate 5
- Dependency Management
- Maven
- Continuing Integration and Delivery
- AWS CodePipeline
- AWS CodeDeploy
- Web Services consumed using Java
- Using ApiMedic a healthservice API thet allows you to access a symptom-checker engine.
- CSS
- Bootstrap 4
- Data Validation
- Bootstrap Validator for front end
- Logging
- Configurable logging using Log4J2. In production, only errors will normally be logged, but logging at a debug level can be turned on to facilitate trouble-shooting.
- Hosting
- Independent Research Topic/s
- CI CodePipeline, CodeDeploy and CodeBuild tools in AWS to build and deploy the application on every commit.
- Project Lombok to eliminate boilerplate code like getters/setters/equals
- Using jQuery to consume internal REST service and handle modal dialog forms
- Unit Testing
- JUnit tests to achieve 80%+ code coverage
- IDE: IntelliJ IDEA
