System Requirements Document (SRD)

Project Name: lemon-erp

1. Introduction

The lemon-erp project is a SaaS-based ERP system tailored for multispeciality hospitals in India. Designed to interlink departments such as IPD (In-Patient Department), OPD (Out-Patient Department), pharmacy, pathology labs, and others, this ERP aims to streamline hospital operations while enhancing patient engagement through web and mobile platforms. Inspired by leading hospital systems like Zydus, Apollo, HCG, and KD Hospital, lemon-erp aspires to set a new benchmark in healthcare technology by addressing both staff and patient pain points.

This document outlines the system requirements for lemon-erp, ensuring alignment with the vision of its creator, Ashissh Pattel, and the needs of its target users.

2. System Overview

lemon-erp is envisioned as a comprehensive, cloud-based ERP solution for multispeciality hospitals. It will integrate all major hospital departments, enabling seamless data flow and real-time collaboration. Additionally, it will include patient-facing features accessible via both web portals and mobile apps, ensuring convenience and transparency for patients.

Key objectives:

• Operational Efficiency: Automate and optimize workflows across IPD, OPD, pharmacy, pathology labs, and other departments.
• Patient Engagement: Provide patients with tools for appointment booking, accessing lab reports, bill payments, and prescription tracking.
• Scalability: Support hospitals of varying sizes, from small clinics to large multispeciality institutions.
• Compliance: Adhere to healthcare regulations and standards in India.
• Accessibility: Ensure usability across diverse demographics, including multilingual support for Indian languages.

3. Functional Requirements

Staff-Facing Features:

• As Admin, I should be able to manage hospital departments, staff roles, and permissions.
• As Doctor, I should be able to access patient records, update treatment plans, and prescribe medications.
• As Nurse, I should be able to track patient vitals and administer prescribed treatments.
• As Pharmacist, I should be able to manage inventory, dispense medications, and track prescriptions.
• As Lab Technician, I should be able to upload test results and manage lab workflows.
• As Receptionist, I should be able to schedule appointments and manage patient check-ins.

Patient-Facing Features:

• As Patient, I should be able to book, reschedule, or cancel appointments via web or mobile.
• As Patient, I should be able to view and download lab reports.
• As Patient, I should be able to pay bills online and access payment history.
• As Patient, I should be able to track prescriptions and receive refill reminders.
• As Patient, I should be able to communicate with doctors for post-discharge care.
• As Patient, I should be able to receive notifications for upcoming appointments, test results, and medication refills.

4. User Personas

Admin

• Role: Oversees hospital operations, manages staff, and ensures compliance.
• Pain Points: Difficulty in monitoring department performance and managing staff efficiently.

Doctor

• Role: Provides medical care, prescribes treatments, and monitors patient progress.
• Pain Points: Limited access to real-time patient data and cumbersome record-keeping.

Nurse

• Role: Administers treatments, monitors patient vitals, and coordinates with doctors.
• Pain Points: Inefficient communication and lack of centralized patient data.

Pharmacist

• Role: Dispenses medications, manages inventory, and tracks prescriptions.
• Pain Points: Inventory mismanagement and prescription tracking errors.

Lab Technician

• Role: Conducts tests, uploads results, and ensures lab efficiency.
• Pain Points: Delays in report generation and lack of integration with patient records.

Receptionist

• Role: Manages appointments, patient check-ins, and initial queries.
• Pain Points: Overbooking and lack of real-time appointment updates.

Patient

• Role: Seeks medical care, accesses reports, and tracks prescriptions.
• Pain Points: Appointment hassles, report delays, billing confusion, communication breakdowns, and lack of transparency in treatment plans.

5. Visuals Colors and Theme

Color Palette:

• Background: #E8F6F3 (Mint Green)
• Surface: #FFFFFF (Pure White)
• Text: #2C3E50 (Midnight Blue)
• Accent: #FF9F43 (Vibrant Orange)
• Muted Tones: #BDC3C7 (Soft Gray)

Theme:

The theme will emphasize clarity, trust, and innovation. The interface will feature clean lines, rounded corners, and subtle gradients to evoke a sense of professionalism and care. The color palette reflects freshness and vitality, aligning with the healthcare domain.

6. Signature Design Concept

Living Blueprint Homepage

The homepage will resemble a dynamic blueprint of a hospital, with animated pencil-sketch designs that morph into real visuals as users interact.

Key Features:

• Interactive Sections: Each department (IPD, OPD, pharmacy, etc.) will appear as a clickable blueprint area. Hovering over a section will animate it into a detailed view with real-time stats and functionalities.
• Patient Journey Animation: A pencil-drawn animation will guide users through a typical patient journey, showcasing how the ERP simplifies each step.
• Time-Based Color Shifts: The background will subtly shift colors based on the time of day (e.g., soft blues for morning, warm oranges for evening).
• Micro-Interactions: Buttons will ripple when clicked, and icons will gently pulse to indicate interactivity.
• Customizable Dashboard: Users can drag and drop widgets to personalize their view, with smooth transitions and animations.

This design will create a memorable first impression, combining creativity with functionality to captivate users.

7. Non-Functional Requirements

• Performance: The system must handle up to 10,000 concurrent users without degradation.
• Security: Implement robust encryption for patient data and comply with Indian healthcare regulations (e.g., HIPAA equivalent).
• Scalability: Support hospitals ranging from 50 to 5000 beds.
• Availability: Ensure 99.9% uptime with disaster recovery mechanisms.
• Localization: Support Indian languages and regional preferences.
• Accessibility: Ensure compliance with WCAG (Web Content Accessibility Guidelines) for users with disabilities.

8. Tech Stack

Frontend

• React for Web
• React Native for Mobile

Backend

• Python
• FastAPI

Database

• MySQL or MariaDB (preferred for RDBMS)
• MongoDB (for NoSQL needs)

AI Models

• GPT 5.4 for user-friendly responses
• Claude 4.6 Opas for coding and academic tasks
• Google Nano Banana for image generation

AI Tools

• Litellm for LLM Routing
• Langchain

Orchestration

• Docker and docker-compose for local development
• Kubernetes for server-side orchestration

9. Assumptions and Constraints

Assumptions

• Hospitals will have internet connectivity to access the SaaS platform.
• Staff will be trained to use the ERP system.
• Patients will have access to smartphones or computers for web/mobile features.
• Hospitals will provide necessary hardware for system integration.

Constraints

• Compliance with Indian healthcare regulations may limit certain functionalities.
• Initial adoption may require integration with legacy systems.
• Data migration from existing systems may involve additional costs and time.

10. Glossary

• ERP: Enterprise Resource Planning
• IPD: In-Patient Department
• OPD: Out-Patient Department
• SaaS: Software as a Service
• HIPAA: Health Insurance Portability and Accountability Act (US equivalent for data protection)
• RDBMS: Relational Database Management System
• WCAG: Web Content Accessibility Guidelines