Software Requirements Specifications
Sanjiveni Project
1. Introduction
1.1 Purpose:
The introduction sets the expectations for the product.
Purpose of the project is to create a software streamline patient health-checkup management for
mobile dispensaries by providing an efficient, lightweight, and user-friendly system for:
Storing and managing patient records
Facilitating diagnosis and prescription workflows
Enabling data analysis for medical trends
This document outlines the functional and non-functional requirements, system features, and
intended use cases.
1.2 Intended Audience: Who is the software for? Who is the end user - whether internally at a
company or externally.
The software will be used by:
1. Doctors to write and store patient details, diagnosis, prescription and access history.
1.2 As well as to prescribe medicine and test.
2. Data Analysts to analyse trends in:
2.2 Disease prevelance
2.3 Prescription Patterns
2.4 Medical Stock Untilization
1.3 Scope: Explain the scope of the software. What are the main goals and objectives? How do they
relate to the company's goals?
Operate on a local server for security and accessibility in mobile dispensaries.
Maintain a relational database for structured patient, medicine, and location data.
Support standardized data entry (dropdown menus, barcode scanning) to minimize errors.
Provide real-time medicine stock and expiry tracking.
Enable quick access to patient history for improved diagnosis.
2. Overall Description: Describe what you are building and for who.
2.1 Product Perspective
The database stores the following information:
1. Location Details:
◦ Location(Dropdown) and Sub-Location(Dependent Dropdown) of the mobile
dispensary at the time.
2. Type of Operation:
◦ OPD
◦ Emergency(Causality)
◦ Health Check Up
3. Patient Queue Management
◦ Registered waiting for the doctor to see them
◦ Patients the doctor is consulting and
◦ Patients that have been diagnosed
4. Patient Details:
◦ Demographic Details: Name, Age, Gender(Text Field)
◦ Medical Data:
▪ Provisional Diagnosis(Dropdown to be selected by doctor)
▪ Secondary Diagnosis(Dropdown to be selected by doctor)
▪ Final Diagnosis(Dropdown to be selected by doctor)
▪ Doctor’s Remarks(Text field for miscellaneous thoughts)
▪ Medicine Prescribed(Dropdown to be selected by doctor)
▪ Tests Prescribed(Dropdown to be selected by doctor)
▪ Date of follow up(Dropdown to be selected by doctor)
◦ Physical Features(eg. Hieght, Weight etc)
◦ Visiting Date
5. Medicine Information:
◦ Number left in stock
◦ Expiry Date(visible when medicine is selected)
2.1 User Needs:
The software should be a tool for data analysis. Standardized Normalised data. Drop down menus
for
Gender
Provisional Diagnosis(Field to be filled by doctor)
Secondary Diagnosis(Field to be filled by doctor)
Final Diagnosis(Field to be filled by doctor)
Medicine Prescribed
Dosage of Medicine
Tests Prescribed
Date of follow up
Location
Sub Location
3. System Features and Requirements
3.1 Functional Requirements:
ID Requirement Description
Standardized Data Dropdown menus for gender, diagnosis, medicine, tests, location,
FR-01
Entry etc.
FR-02 Dependent Dropdowns Sub-location updates based on selected location.
Categories → Medicine → Dosage selection. Stock & expiry
FR-03 Medicine Management
visibility.
FR-04 Patient History Access Quick retrieval of past visits, prescriptions, and test results.
FR-05 Barcode Integration Scan patient IDs to auto-fill details.
3.2 External Interface Requirements:
The system will be connected to a barcode scanner to fill out patient details.
Large font sizes for readability.
3.3 Non-functional Requirements:
It is a lightweight software which should be able to support a fast paced usage. There cannot be
any tolerance for bugs or crashes. It must be usable by doctors reliably.
Password Protected. Password must be changed regularly.