Project: Doc’IT

Doc’it provides a centralised platform for authorised staff from small family clinics to view, update, and onboard patient records and schedule appointments, solving the inefficient paper records and files used today. With Doc’it, small family clinics can reduce man-hours in managing paper files, translating this ‘saved’ time into better frontline care services.

Given below are my contributions to the project.

  • New Feature: Added the Prescription class
    • What it does: allows the user to record down prescriptions given to the patient.
    • Justification: This allows medical professionals to record down prescriptions provided to patients during each appointment. It also allows them to check past prescription histories of patient.
    • Highlights: This enhancement requires careful navigation of nested lists structures and modifies the storage serializer to deal with this structure.

  • Code contributed: RepoSense link

  • Project management:
    • Managed releases v1.1 - v1.4 (4 releases) on GitHub
  • Enhancements to existing features:
    • Wrote additional tests for existing features to increase coverage from 66% to 76% (Pull requests #59, #277)
  • Documentation:
    • User Guide:
      • Added documentation for the features add prescription and delete prescription #181, #306
    • Developer Guide:
      • Wrote target user profile, value proposition and user stories. #37
      • Created Plant-UML diagrams for prescription class. #181, #306
      • Added implementation details of the prescription feature. #181, #306
  • Community:
    • PRs reviewed (with non-trivial review comments): #44, #282
    • Contributed to forum discussions (examples: 1, 2, 3)
    • Reported bugs and suggestions for other teams in the class (examples: 1, 2, 3)
  • Testing:
    • Designated as main tester for team, in charge of testing and finding ways to break our app.
    • Contributed to more than 42% of all bug related issues raised for team. (examples: 1, 2, 3)
    • Emphasized on KISS design principle to team during high level design meetings.
    • Input validation: Implemented more restrictive general parsing to reduce likelihood of unintended inputs. #232
    • Introduced more restrictive parsing guidelines for prescriptions. #274
    • Initiated discussions on forum regarding sustainable testing rigor across development life cycle. (Link here)