Requirements

MoSCoW Requirements


The MoSCoW requirements listed have been discussed and agreed with the clients.

However, the requirements may be subjected to change as we progress with our project.

OpenMRS Platform

OpenMRS Android App


OpenMRS Platform

ID Requirements Type Category Priority
UI/UX
P1 The OMRS platform shall register new patients/health providers Functional UI/UX Must
P2 The OMRS platform shall provide different access point for different users Functional UI/UX Must
P3 The OMRS platform shall allow patient to save filled forms Functional UI/UX Must
P4 The OMRS platform shall allow patient to continue filling forms that was saved Functional UI/UX Must
P5 The OMRS platform shall support data integrity with server Functional UI/UX Must
Data Storing
P6 The OMRS platform shall allow patient to fill data manually Functional Data Storing Must
P7 The OMRS platform shall store patient's basic data Functional Data Storing Must
P8 The OMRS platform shall store patient's vitals Functional Data Storing Must
P9 The OMRS platform shall store patient's visits Functional Data Storing Must
P10 The OMRS platform shall store patient's daily activity log Functional Data Storing Must
P11 The OMRS platform shall store patient's food plan log Functional Data Storing Must
P12 The OMRS platform shall store patient's water log Functional Data Storing Must
P13 The OMRS platform shall store patient's heart rate Functional Data Storing Must
P14 The OMRS platform shall store patient's sleep log Functional Data Storing Should
P15 The OMRS platform shall store patient's health conditions Functional Data Storing Could
P16 The OMRS platform shall store patient's sharing preferences Functional Data Storing Should
Data Viewing
P17 The OMRS platform shall allow health provider to view patient's data Functional Data Viewing Must
P18 The OMRS platform shall only allow authorized health provider to view data Functional Data Viewing Should
Data Visualisation
P19 The OMRS platform shall display a graphical representation of data given Functional Data Visualisation Could
Data Downloading
P20 The OMRS platform shall allow health provider to download patient's data Functional Data Downloading Should
Security
P21 The OMRS platform shall support persistence of user session Non-Functional Security Could
P22 The OMRS platform shall support expiry of user session Non-Functional Security Could

Back to top


OpenMRS Android App - Patient Version

ID Requirements Type Category Priority
UI/UX
A1 The OMRS patient app shall register new patients/user Functional UI/UX Must
A2 The OMRS patient app shall allow user to choose pop-up notification Functional UI/UX Would
A3 The OMRS patient app shall provide health & nutrition tips Functional UI/UX Could
A4 The OMRS patient app shall support data integrity with OMRS platform Functional UI/UX Must
Data Storing
A5 The OMRS patient app shall allow user to choose health provider to share data with Functional Data Storing Would
A6 The OMRS patient app shall allow manual data entry Functional Data Storing Must
Data Viewing
A7 The OMRS patient app shall display daily statistic Functional Data Viewing Would
A8 The OMRS patient app shall display weekly statistic Functional Data Viewing Would
Data Visualisation
A9 The OMRS patient app shall display graphical representation of data stored Functional Data Visualisation Could
Data Synchronisation
A10 The OMRS patient app shall sync data from GoogleFit Functional Data Synchronisation Must
A11 The OMRS patient app shall sync data from FitBit Charge HR Functional Data Synchronisation Must
A12 The OMRS patient app shall sync data from MyFitnessPal (V2) Functional Data Synchronisation Would
A13 The OMRS patient app shall integrate with Google Calendar (V2) Functional Data Synchronisation Could
Data Analytics
A14 The OMRS patient app shall provide health & nutrition feedbacks Functional Data Analytics Could
Data Deletion
A15 The OMRS patient app shall allow user to delete account Functional Data Deletion Could

Back to top