Table 2 Functional and non-functional requirements
Functional requirements | o Possibility of recording clinical and demographic data in a structured way and creating a medical record for each patient o Preparing automatic reports on the latest status of patients based on different groups o Creating a smart form for collecting patient data for each patient based on her/his health status o Immediately alert physicians regarding the patient’s need for more assessment or if not an eligible candidate o Categorizing patient information and test results and making related suggestions for better clinical decision-making in different circumstances o Proposing the most suitable transplant candidate based on blood type matching and required information o Automatically create a transplant day form for the selected patient based on the latest recorded information and send it to transplant team members to save time o Creating automatic statistical reports |
Non-functional requirements | o Online, fast, and easy access to patient data from anywhere at any time (High Availability) o Stepwise physician guidance on how to evaluate patients with different conditions and diseases by answering different questions (Performance) o Sending an automatic message to the patient to be selected as a transplant candidate for a routine office visit (Reliability) o Need to create an environment such as a chat room to discuss and coordinate between team members (Usability) o Easy navigation between different forms and sections (Performance) |