Project: Patient Book

Patient Book is an app for managing patient’s information including personal details, appointment details and medical histories, optimized for use via a Command Line Interface (CLI) while still having the benefits of a Graphical User Interface (GUI).

Contributions to the project.

  • New Feature: Added the ability to view medical records #46)
    • What it does: Allows the user to view patient medical records they added by using the command given. They will see the medical record of a patient listed on the UI.
    • Justification: This feature will allow user to view the important medical records they added.
    • Credits: N/A
  • New Feature: Added the ability to add appointment #51)
    • What it does: Allows the user to add appointment to the patient using the command given.
    • Justification: This feature will allow user to add appointment they their have.
    • Credits: N/A

  • Code contributed: RepoSense Link

  • Project management
    • Managed releases v1.0 - v4.0 (4 releases) on Github
  • Enhancements to existing features:
    • Enhanced the Appointment functionality to allow adding appointment records.
    • Enhanced the Medical Records functionality to allow viewing of medical records.
  • Documentation:
    • User Guide:
      • Added documentation for the features Add Medical Records (#56)
      • Added documentation for the features View Medical Records (#56)
      • Added documentation for the features Delete Medical Records (#56)
      • Added documentation for the features view Appointment on Today (#56)
    • Developer Guide:
      • Added user stories for Add/View/Delete Medical Records (#56)
      • Added documentation for the features Add Medical Records (#56)
      • Added documentation for the features View Medical Records (#56)
      • Added documentation for the features Delete Medical Records (#56)
      • Added documentation for the glossary section (#30)
  • Community:
    • Our application was developed using a combination of pair-programming and adhoc coding sessions. During each session lasting between an hour to four or more, all group members sat in a meeting session while coding/ implementing their assigned components. If a concern was raised or support was needed, they shared their screen via the meeting session and everyone participated or assisted to clear the obstacle. Using this method we’ve successfully cleared v1.0 to v3.0 of our project milestones.