Clinics Management System (CMS)

Group Members
1. Joni Vrushi
2. Andi Bulaj
3. Gerald Toto
 Table of Contents
1. Summary………………………………………………….3
1.1.Project Overview…………………………………….. 3
2. Requirements……………………………………………...4
2.1 Functional Requirements……………………………...5
2.2 Non-Functional Requirements………………………...9
3.Software Design…………………………………………...11
3.1 Use Cases…………………………………………….11
3.2 Bpmn…………………………………………………14
3.3 Activity Diagrams……………………………………15
3.4 State Diagrams……………………………………….34
3.5 Sequence Diagrams………………………………….36
3.6 Collaboration Diagrams……………………………..44
3.7 Class Diagrams……………………………………...48
3.8 ERD…………………………………………………50
3.9Deployment…………………………………………..51
 1.Summary
1.1 Project Overview
Purpose:
The Clinics Management System (CMS) is a comprehensive software
solution designed to streamline and enhance the operations of a
healthcare facility. This system is tailored to address the specific needs
of clinics by efficiently managing employee information, financial
responsibilities, appointment scheduling, and patient health records.
With a user-friendly interface, the CMS aims to improve the overall
efficiency, organization, and service delivery within the clinic.
Key Features:
Employee Information Management:
 Store and manage detailed information about each employee,
including personal details, roles, and responsibilities.
 Track employee attendance, work hours, and performance
records.
Financial Duties Management:
 Facilitate financial tasks such as invoicing, billing, and payment
tracking.
 Generate financial reports to provide insights into the clinic's
financial health.
Appointment Scheduling:
 Maintain a centralized schedule for all clients, appointments, and
meetings.
 Automatically send reminders to clients one day before their
scheduled appointments, ensuring timely attendance and
reducing no-shows.
Health Data Storage:
 Create a secure and organized repository for storing all health-
related data for each patient.
 Categorize and manage patient records based on their medical
history, treatment plans, and prescribed medications.

2.Requirements
2.1 Functional Requirements
2.2 Non-Functional Requirements
1. User Interface:
 The system should provide responsive user interfaces, with a
maximum response time of 2 seconds for standard operations.
 The user interface should be intuitive and user-friendly, requiring
minimal training for new staff members.
 The system should be compatible with the latest versions of
popular web browsers (e.g., Chrome, Firefox, Safari).
 It should be accessible from both desktop and mobile devices
without compromising functionality.
 The system should comply with accessibility standards, ensuring it
is usable by individuals with disabilities.
2. Performance:
 It should handle a minimum of 100 concurrent users without
degradation in performance.
 The system should have a minimum uptime of 99.9% to ensure
continuous availability.
3. Security:
 All patient data should be stored securely, following industry-
standard encryption protocols.
 Access to sensitive information should be role-based, ensuring
that only authorized personnel can view and modify patient
records.
 The system should support audit trails to track changes to patient
records for compliance and accountability.
 The system should adhere to relevant healthcare data protection
regulations and standards.
4. Backup and Recovery:
 It should include automatic backup and recovery mechanisms to
prevent data loss in case of system failures.
5. Compatibility:
 The system should be compatible with the latest versions of
popular web browsers (e.g., Chrome, Firefox, Safari).
6. Usability and Training:
 The user interface should be intuitive and user-friendly, requiring
minimal training for new staff members.
7. Documentation:
 The codebase should be well-documented to facilitate easy
maintenance and updates.
8. Updates and Maintenance:
 Regular software updates and patches should be easily deployable
without disrupting daily clinic operations.
9. Regulatory Compliance:
 The system should adhere to relevant healthcare data protection
regulations and standards.
10. Reporting:
 The system should provide comprehensive reporting capabilities,
allowing administrators to generate performance reports,
financial summaries, and patient analytics.
 3.Software Design
3.1. Use Cases
 Admin Use Case
 Client Use Case
 Worker Use Case

3.2 BPMN
3.3 Activity Diagrams
 Admin Accept/Denies Workers request
 Admin Creates/Deletes Workers account
 Financial Document
 Admin Receives/Send requests to Workers
 Admin Sends documents to Workers
 Admin Checks supplies
 Admin Views equipment lifespan
 Client Communicate with Worker
 Client Views Invoices
 Client Views/Receives info about appointments
 Worker Communicate with Client
 Worker Creates Client account
Worker Creates/Views Clients health records
 Worker Creates/Views invoices
 Worker Receives/Send documents to Admin
 Worker Receives/Sends request to Admin
 Worker Views health records
3.4 State Diagrams
 Admin State Diagram
 Client State Diagram
 Worker State Diagram
3.5 Sequence Diagrams
 Admin Add/Views Finances
 Admin Creates/Deletes Workers account
 Admin Views Equipments and Supplies
 Admin Receives/Sends things
 Client views client Documents
 Worker Creates/Deletes Client account
 Worker Receives/Sends Documents from Admin
 Worker Adds/Views Clients Documents
3.6 Collaboration Diagram
 Admin Adds/Views Finances
 Admin Creates/Deletes Workers account

 Admin Views equipments and supplies

3.7 Class Diagram