System Requirements Document for dawai-setu

1. Introduction

DAWAI-SETU (Drug Availability Watch & Inter-facility Transfer Utility) is a responsive healthcare web application designed to address the problem of emerging medicine shortages in the Mangalore–Udupi–Manipal region. The application aims to detect shortages early, forecast stockout risks, identify regional patterns, find available surplus, recommend redistribution or intervention, and track transfers until the receiving facility gets the stock. The target audience includes hospital managers, pharmacy or medicine dealer managers, laboratory or blood bank managers, and regional admins or authorities.

2. System Overview

DAWAI-SETU is a web-based application that uses simulated healthcare supply-chain data to manage and monitor the availability of medicines and blood across various facilities. The system provides role-based access to different users, enabling them to manage inventories, detect risks, and facilitate the redistribution of resources. The application is designed to be modern, responsive, and accessible, with a focus on providing a seamless user experience for healthcare professionals.

2a. Product Interpretation and Delivery Boundary

The application is designed to operate within the Mangalore–Udupi–Manipal region, using simulated data for 500+ medicines and 40+ healthcare facilities. It provides role-specific workspaces for hospital managers, pharmacy or medicine dealer managers, laboratory or blood bank managers, and regional admins or authorities. The application requires user authentication and authorization, with role-based permissions for accessing different features. The system does not integrate with real-world services like Swiggy Genie unless explicitly connected via an API.

2b. Source Content Inventory

Not applicable as no content_source directive is provided.

2c. Page Content and Component Coverage

Landing

• Information: Overview of DAWAI-SETU, its purpose, and the healthcare audience.
• Components: Introduction to the simulated regional network and shortage-prevention workflow.
• Access: Public entry surface.

Login / Registration

• Information: User registration and login interface.
• Components: Role selection (Hospital, Pharmacy, Laboratory, Medicine Dealer), user details collection, OTP verification.
• Access: Identity access surface.

Dashboard

• Information: Role-based operational summary.
• Components: Total medicines, critical medicines, at-risk medicines, surplus medicines, expiring medicines, active transfers, incoming/outgoing requests, regional shortage alerts, AI summary.
• Access: Role-restricted.

My Hospital

• Information: Hospital-specific operational context.
• Components: Medicines, Blood Bank, hospital resources.
• Access: Role-restricted to Hospital Managers.

Medicines

• Information: Medicine inventory management.
• Components: Stock, consumption, replenishment, expiry, criticality, risk, AI explanations, recommended actions.
• Access: Role-restricted.

Blood Bank

• Information: Blood inventory management.
• Components: Blood groups, available/reserved units, demand, expiry, incoming stock, risk, transfer participation.
• Access: Role-restricted.

My Company/Pharmacy Inventory

• Information: Pharmacy and medicine dealer inventory management.
• Components: Medicine inventory, surplus/shortage identification, stock offers/requests.
• Access: Role-restricted to Pharmacy or Medicine Dealer Managers.

Regional Redistribution

• Information: Search and comparison for medicine and blood resources.
• Components: FEFO-aware matching, recommendations, offer/request actions.
• Access: Role-restricted.

Regional Blood Network

• Information: Connection of participating hospital and regional blood facilities.
• Components: Blood network management.
• Access: Role-restricted.

Regional Map

• Information: Interactive map of the region.
• Components: Facility markers, search, zoom, filters, inventory and transfer inspection.
• Access: Role-restricted.

Facility Network

• Information: Directory of regional facilities.
• Components: Facility details, classifications, resources, shortages, surplus, network status.
• Access: Role-restricted.

Inbox

• Information: Role-relevant communication.
• Components: Requests, offers, alerts, approvals.
• Access: Role-restricted.

Inbox/Requests

• Information: Pharmacy and dealer communication.
• Components: Requests, offers, alerts, approvals.
• Access: Role-restricted.

Transfers

• Information: Transfer lifecycle management.
• Components: Approval, pickup, transit, delivery, receipt, inventory update.
• Access: Role-restricted.

Alerts

• Information: Network shortage and risk management.
• Components: Risk progression, what-if scenarios, escalation, intervention recommendations.
• Access: Role-restricted.

History

• Information: Transfer and delivery audit trail.
• Components: Transfer ID, medicine/blood details, source, destination, quantity, date/time, status, approval, delivery.
• Access: Role-restricted.

3. Functional Requirements

1. As a Hospital Manager, I should be able to manage hospital medicine and blood inventories, review stockout risk and AI explanations, offer or request stock, approve outgoing transfers, receive incoming transfers, and verify that received stock updates inventory and risk.

   • Provenance: Explicit
   • Lifecycle: Initiate inventory management, review risks, make decisions on stock offers/requests, approve transfers, update inventory upon receipt.
   • Acceptance: Inventory and risk updates are reflected accurately.

2. As a Pharmacy or Medicine Dealer Manager, I should be able to manage medicine inventory, identify safe surplus or impending shortages, offer, request, and supply stock through regional matching, and track transfers through delivery.

   • Provenance: Explicit
   • Lifecycle: Manage inventory, identify surplus/shortages, initiate offers/requests, track transfer status.
   • Acceptance: Accurate tracking and inventory updates.

3. As a Laboratory or Blood Bank Manager, I should be able to manage blood inventory, monitor blood-group demand, expiry and risk, participate in the Regional Blood Network, and offer or request blood transfers through receipt.

   • Provenance: Explicit
   • Lifecycle: Monitor blood inventory, manage risks, participate in network, manage transfers.
   • Acceptance: Effective management of blood inventory and network participation.

4. As a Regional Admin or Authority, I should be able to monitor the complete regional network, facilities, maps, shortages, alerts, transfers, and intervention recommendations, including emerging regional shortage progression and escalation.

   • Provenance: Explicit
   • Lifecycle: Monitor network, analyze data, make intervention decisions, escalate issues.
   • Acceptance: Comprehensive oversight and timely interventions.

5. As a user, I should be able to register and log in to the application using role-specific onboarding, including manager/user name, facility/company name, facility type, and email or phone, with simulated verification-code/OTP account verification.

   • Provenance: Explicit
   • Lifecycle: Register, verify account, access role-specific features.
   • Acceptance: Successful registration and access to features.

6. As a user, I should be able to request location permission and have my area classified as Urban, Semi-Urban, or Rural using nearby healthcare-facility density, with this classification shown in my profile and used in risk/logistics calculations.

   • Provenance: Explicit
   • Lifecycle: Request location, classify area, use classification in calculations.
   • Acceptance: Accurate classification and usage in calculations.

4. User Personas

Hospital Manager

• Context: Manages hospital medicine and blood inventories.
• Primary Goal: Ensure adequate stock levels and manage risks.
• Responsibilities: Review stockout risks, offer/request stock, approve transfers, update inventory.
• Interactions: Collaborates with other facilities for stock management.
• Success: Maintains optimal inventory levels and reduces stockout risks.

Pharmacy or Medicine Dealer Manager

• Context: Manages medicine inventory for pharmacies or dealers.
• Primary Goal: Optimize inventory levels and manage surplus/shortages.
• Responsibilities: Identify surplus/shortages, manage offers/requests, track transfers.
• Interactions: Engages with regional network for inventory management.
• Success: Efficient inventory management and timely transfers.

Laboratory or Blood Bank Manager

• Context: Manages blood inventory and participates in the Regional Blood Network.
• Primary Goal: Ensure adequate blood supply and manage risks.
• Responsibilities: Monitor blood demand, manage risks, participate in network, manage transfers.
• Interactions: Coordinates with other blood facilities for resource sharing.
• Success: Maintains sufficient blood supply and reduces risks.

Regional Admin or Authority

• Context: Oversees the regional healthcare network.
• Primary Goal: Monitor and manage regional shortages and interventions.
• Responsibilities: Analyze network data, make intervention decisions, escalate issues.
• Interactions: Collaborates with facility managers for regional management.
• Success: Effective regional oversight and timely interventions.

5. Core User Flows

5.1 Hospital Manager Inventory Management

1. Start: Hospital Manager logs into the Dashboard.
2. Action: Reviews inventory levels and AI risk analysis.
3. Decision: Identifies critical shortages or surplus.
4. Action: Offers surplus or requests additional stock.
5. Outcome: Approves outgoing transfers and receives incoming transfers.
6. Completion: Inventory and risk levels are updated.

5.2 Pharmacy Manager Surplus Management

1. Start: Pharmacy Manager accesses the My Company/Pharmacy Inventory page.
2. Action: Reviews inventory for surplus or shortages.
3. Decision: Initiates offers or requests based on inventory status.
4. Action: Tracks transfer status through the Transfers page.
5. Outcome: Inventory is adjusted based on transfer completion.
6. Completion: Surplus and shortage levels are managed effectively.

5.3 Blood Bank Manager Network Participation

1. Start: Blood Bank Manager logs into the Blood Bank page.
2. Action: Monitors blood inventory and demand.
3. Decision: Identifies risks and participates in the Regional Blood Network.
4. Action: Offers or requests blood units as needed.
5. Outcome: Manages transfers and updates inventory.
6. Completion: Blood supply is maintained, and risks are minimized.

5.4 Regional Admin Network Monitoring

1. Start: Regional Admin accesses the Dashboard.
2. Action: Monitors regional network data and alerts.
3. Decision: Analyzes data for emerging shortages and interventions.
4. Action: Makes intervention recommendations or escalates issues.
5. Outcome: Regional network is managed effectively.
6. Completion: Shortages are addressed, and interventions are implemented.

6. Visuals Colors and Theme

• Muse: Yves Béhar
• Palette:
  • Background: #FFFFFF
  • Surface: #F7F5F2
  • Text: #333333
  • Primary: #784212
  • Accent: #A5BB5E
  • Muted: #D4CBBE
• Typography:
  • Headings: Work Sans, Medium weight, large sizes, loose tracking, sentence case
  • Body: Karla
  • Scale: 1.414 modular, 48/34/24/16/14
• Shape Language: Rounded product-led heroes, soft cards, human-scale spacing
• Layout: Modular grid with clear sections, soft cards for data presentation, generous margins
• Motion: Breathing, slow easing transitions for a wellbeing pace

7. Signature Design Concept

The landing page will feature a full-width hero section with an interactive map of the Mangalore–Udupi–Manipal region. The map will be layered with data visualizations of current inventory status, using primary and accent colors to highlight key areas. Rounded cards with soft shadows will display facility details, and traffic-light indicators will show risk and inventory levels. AI insight panels will present data in a humanistic manner, with smooth, breathing animations for transitions and data updates.

8. Interaction Model & Motion Direction

• Interaction Model: Static
• Motion Tempo: Restrained
• Hero Dimensionality: Layered_2d
• Landing Hero Motion Brief: The focal subject is the interactive regional map, which transforms to show detailed inventory status upon user interaction. The motion vocabulary includes smooth transitions and breathing animations, with a composed first frame showing the region's overview. A reduced-motion state will be available for accessibility.

9. Non-Functional Requirements

1. Responsiveness: The application must be fully responsive, adapting to various screen sizes and devices.

   • Provenance: Explicit
   • Rationale: Ensures accessibility and usability across different platforms.

2. Accessibility: The application must meet accessibility standards to ensure usability for all users.

   • Provenance: Explicit
   • Rationale: Provides an inclusive user experience.

3. Data Labeling: All displayed network and inventory records must be clearly labeled as simulated/demo data.

   • Provenance: Explicit
   • Rationale: Ensures transparency and clarity for users.

10. Tech Stack

• Frontend: React
• Backend: Python/FastAPI
• Database: PostgreSQL
• Deployment: Docker, Kubernetes (if required)
• Simulated Data: Clearly labeled as demo data

11. Assumptions and Constraints

• Assumption: Users will have internet access to use the web application.
• Constraint: The application will only use simulated data for the prototype.
• Assumption: Users will provide location permissions for accurate classification and logistics calculations.

12. Glossary

• AI Risk Analysis: The process of evaluating the risk of stockouts using artificial intelligence.
• FEFO: First Expiry, First Out; a principle for managing inventory based on expiry dates.
• Regional Blood Network: A network connecting hospital and regional blood banks for resource sharing.
• Simulated Data: Data used for testing and demonstration purposes, not real-world data.