200120107530 1.2 Scope: -Bei this necator see ee role, hospital management graduates can enter into level of the compan ED he levels right from middle level management to the top editicare Rector hes ane the scope gets increased. Also, as management in the atiente:the poe ly an care of after direct medical services provided to the diversification intra ea is have good opportunity to expand their career with Seah oe pat inter institutes. Because of entrance of private players in the Rearing Pe sate quality health care services at low cost, the experienced and Sa les are taken in hands for a particular position. On the other side ith increasing efforts of the government, the rural and urban health care is also gaining its importance and graduates in this field have more chances of getting employment 1.3 Product Scope: - Currently Wennapuwa St Joseph hospital is using a manual system 'o handle the hospital process. When patients arrive, they make an appointment! at the reception to Consult a doctor. These are being recorded in a file. Then again, the patients diagnosed symptoms related disease details, ward details ‘and other necessary details are being recorded and those files are being stored in special locations. Calculation of bills and inventory are done manually. As the current system is 2 file based one management of the hospital has to put much effort on securng the files. They can be easily damaged by fire, insects and natural disasters. A\s@ could be misplaced by fosing data and information. Limited storage space of the files is another issue that they currently face when the management is manually done There occurs an issue with the organization of data information and schedules and running the process methodically Which leads to the manual system malfunctioning, tfwe want to check a previous record of a patient or other detail. Management will be in a great problem. I's a tough and time taking process to search for a record in a file Keeping files takes much time and waste much precious Mat hours. The tendency of functioning manually. It is hard to relay on the accuracy making mistakes is high when Tealeulations done manually too. Its more obvious for problems to arise. We plan to cyercome the above mentioned problems through a standalone application, to manage the major functions of the Hospital System. The hospital management system we are going to implement will be covering all basic processes done in the hospital. It would pence Employee and Salary management, Patient and “Zumba exercise” management, Theatre and ward Management, Laboratory management, Transport Management, Pharmacy Management, OPD management and emergency management. In OPD unit, with the OPD and Consultation 200120107530 3150711 SE200120107530 Management system, thi automated. So the staff sh ean channeling details enteringprocess has ErZiLeidatiig lier In fies, Arc itu purmber mauivo crceoe Oa sppoinument 1eteans - efficient. And keeping the track A oe issuing process becomes easier and Rifai tis detalle whenaver ee ie and medical prescription details allow them ~ iManegamant system we record yen implementing the Employee & Salary ‘ falling Uociors'echedules, Arid th lance, shifting of employees, their holidays and | Oi cioure/ Shares of consulthig ae an performs calculations of EPF/ETP and “ Rear risirelabisaniiceciaieas ik rs and do the payroll part. This is more efficient pe are cieairrest, The prapeaed : an avoids incorrect data inputs whenever delatie of surgeons, in- patient ystem for Mini-theatre & Ward Management records surgery details. The ph patients who are assigned for Wards, different ward details and Beers far the pI ae used within the theatre are managed as well Pepe haya cite i ients according to their diseases based on wards Is systemized gees are well = ina systematic way. So the details of surgeons. patients and Pecorino ganized and can be easily accessed whenever needed Surgery ree progress reports, In-ward patient progress details are generated and istory can be tracked too. The Vehicle & Transport Management systc™ handles all the data on ambulance transport. It manages the time slots of ambulances driver's and | employee details of transportsection and provides bill generating facility. And reliable Fl time slot management provides the facility of checking the availability of the i ambulances whenever required, and decide about a possible time they can fulfill a request. The current process of “Zumba” exercise details managing does not support for any individual progress analyzing. The Exercise “Zumba” Management provides @ Lon detailed progress report of each individual and allows the management or their customer to take decisions on exercise plans. The system developing for Emergency Treatment & Equipment Management automate the current processes of patient registering and propose a better way {0 keep records of equipment and medicines on related to the emergency treatment unit in a ‘computer based file system, The proposed ud system provides a simple interfaceto gather quick information of the patient and record | them. So that in a case of special request by an external party, details of the patient history can be accessed and viewed The Pharmacy Stock Management system Is | responsible for proper management of drug stocks,pop ups the notifications of expiry a7 dates of stock items. This system allow the to keep track of medicine stocks | notify the personals when the stock i ing out of items and help the manager to reduce stock levels and eli Stock waste. The Lab Management System records sample collection details, keep track of lab resources and participate in lab reports + oJ conclusion generating. This increases the accuracy of report generating process and save a lot of time in manual handling of report details and improve the efficiency and - the productivity of the organization. Our goal is to make a client satisfied system by full | filling the client requirements and improving the current manual system with client | f what we have suggested by ae needs which are not even particularly mentioned but y the client to improve the standard of the system and of analyzing and got approved b} the management of the hospital to its utmost. The scope of the SRS is basically for everyone involved to understand and have an idea about how and what is going to | happen in the system. Using ER, User Case diagrams and GU!'s which are in a form is where everyone can understand. How the interfaces finally appear. To have an idea . about the new employees that the client might have to get employed when the system is implemented. 200120107530 3190711 SE z “ =P eet200120107530 4.4 Assumption and dependencies: - @ Each user must have a valid user id and password © Server must be running for the system to function Users must log in to the system to access any record @ Only the Administrator can delete records 1.5 Overview: - A hospital management system (HMS) is a computer or web based system that facilitates managing the functioning of the hospital or any medical set up’. ... It integrates all the information regarding patients doctors, staff hospital administrative details etc. into one software200120107530 Practical No. 2 Software Requirement Specification Aim: Prepare Software Requirement Specification (SRS) document for chosen application Exercise: Create a SRS document for selected application A) Meaning of SRS Documen :- A software requirements specification (SRS) is 2 document that describes what the software will do and how it will be expected to perform. It also describes the functionality the product needs to fulfil all stakeholders (business users) needs A typical SRS includes: @ A purpose e An overall description © Specific requirements The best SRS documents define how the software will interact when embedded in hardware — or when connected to other software. Good SRS documents also account for real-life users Table of Contents: 1. Introduction 1.1 Purpose 1.2 Scope 1.3 Product Scope 1.4. Assumption and dependencies 15 Overview200120107530 2. Overall Description 2.1 Product Perspective 2.2 Product Functions 23 Operating Environment 2.4 Assumptions and Dependencies 3. System Features 3.1 Functional Requirements 4. External Interface Requirements 4.1 User Interface 4.2 Hardware Interfaces I ) 4.3. Software Interfaces 5. Non-functional Requirements 5.1 Performance Requirements 4 5.2 Safety Requirements 5.3 Security Requirements Chapter 1 Introduction 2 Be | 1.1 Purpose: - : © Processing Speed & Results © Cost Effective | @ Reduction in Errors © Data Security & Retrieving Ability @ Improved Patient Care © Quality & Compliance 3160711 SE 200120107530200120107530 Chapter 2 Overall Description 2.1 Product Perspective - be ee er aes Centre follows manual procedures to keep track of its day to day jen Scenarios such as patient information handling, employee handling stock handling, financial analysis and report generation is taken into consideration there exists many issues with regard to efficiency, security, accuracy and reliability Due to improperly managed details medical center faces quite a lot of difficulties in accessing past data as well as managing present data, The manual file systems which are being used at present require storage facilities which is also another overhead The fully functional automated hospital management system which will be developed through this project will eliminate the disadvantages caused by the manual system by improving the reliability, efficiency and performance, The usage of a database to store patient, employee. stock details etc. will accommodate easy access. retrieval search 3nd manipulation of data. The access limitations provided through access privilege levels will enhance the security of the system. The system will facilitate concurrent access and convenient management of activities of the medical center 2.2 Product Functions:- OPD and Consultation Management : - Recording patient details Issuing numbers according to doctor channeled Updating the record with medical prescription Fe Printing bill of doctor charges @ Attendance and schedule of employees © Holiday approvals ¢ Schedule of consulting doctors © EPF/ETP and OT calculation 200120107530 3980711 SE200120107530 © Shares of consulting doctors ¢ Shares of doctors who has sent patient for lab test and ECG Mini Theatre and Ward Management: - © Details of surgeon © Surgery success/failure details © Complications of the patient, patient history and other details © Bill calculation and reports Vehicle and Transport Management: - Ambulances management © Vehicle deployment handling ‘© Time management © Drivers and employee details © Billing calculations ind Patient Manage! ‘umbi Exercise ent © Patient management © Weight loss and height increase © Abdominal circumference © Progress report 200120107830 3180711 SE hui samen ie200120107530 © Package details Emergency Treatment and Equipment Management. - © Emergency patient Details @ Issue ECG reports © Billing calculations @ Lab equipment stock management Pharmacy Stock Management - - ‘© Drug stock management ‘@ Expiry notification © Billing calculation © Searching Lab Management : - © Record sample collection details ¢ Lab resources management tion © Lab report conclusion general © Bill calculation @ Lab equipment stock management 200120107530 3150711 SE core 1200120107530 2.3 Operating Environment Software requirements : - Windows 7 or above operating system . JRE 18 © MySQL server Hardware Requirements * - © Core iS processor © = 4GB Ram 200120107530 pel200120107530 ° 20GB of hard disk space in terminal machines . 1TB hard disk space in Server Machine 2.4 Assumptions and Dependencies : - . Each user must have a valid user id and password ¢ Server must be running for the system to function _Users must log in to the system to access anyrecord Only the Administrator can delete records Chapter 3 System Features 3.1 Functional Requirements : - There are a lot of software requiremen requirements of the Hospital Management namely Registration, Check out, Report Gener ts specifications included in the functional System, which contains various process ation, and Database Registration Process of SRS (Software Requirements Specification) * Adding Patients: The Hospital Management enables the staff in thefront desk to include new patients to the system. Assigning an ID to the patients The HMS enables the staff in thefront desk to provide a unique ID for each patignt and then add them to the record sheet of the patient. The patients can utilize the ID throughout their hospital stay. Check Out of SRS: The staff in the administration section of the wardcan delete © Deleting Patient ID: em when the patient's checkout from the hospital the patient ID from the syst s available list: The Staff in the adi ty in the list of beds-available - Adding to bed ministration sectionof the ward can put the bed emp! 120107530 3150711 SE200120107530 : ’ Practical No. 3 Entity-Relationship Diagram and Class Diagram Aim: Draw E-R diagram and class diagram for chosen application Exercise: Draw E-R diagram and class diagram for your selected application 41. E-R Diagram for Hospital Management System 3180711 SE200120107530 2. Class Diagram for Hospital Management System eon ica =) ‘sting So lea middletvame sting organi mame FullName q homeAdsress tname Fullname sgender Gender spntnDate Dale te Integer accepted Date sickness History prescriptions’ stenal,] Slierges — Stenal| SpeaaiRegs Stal") ‘operations ‘Stat Doctor vaity strnal’) fecations. sina are Technician, | Front Desk | | nurse [ge (ee CN Technotogist |200120107530 Practical No. 4 Use Case Diagram Writ Aim: Write Scenario and draw Use Case Diagram for chosen application Exercise 4. Scenario for Hospital Management System for XY Hospital, where | departments in the hospital. ment tasks. Most and rehensive software product ere are several ing the patient appoint tt However, patients can walk in We want to develop a compr several doctors are working together. Th but a central administration office is handl patients make an appointment before their vis! can be treated if an appropriate doctor is available their visit schedule ar should cancel his/| patient who made by calling. A f to atients may change ut cannot appe: her appointment In order penalty On events, Pi an appointment b avoid a ‘no-show’ ‘andling all the appointments rks in the administration office are h lerks generate ‘daily treatment schedules’ for doctors based on include doctor's name, patient's atment. Hence doctors are The appointment clel and the scheduling © the appointment. The information, nurses and treatment 10" seeing patients according to the daily treat! 31go711 SEyy “dl ‘530 : 10107! ot Use Case Diagram for Hospital Management System 2. us! | USecose- 5 ( Deda oppetintrned | Q- K Wo S Reception: £ cketod (Js | 1 Z A pexeption )* | se i ahival ‘ onder 90 i; \ poucy Opevadon C rend ditvchase/90120107530 2 Practical No. 5 Activity Diagram aim: Draw Activity diagram for selected application i Exercise: Activity Diagram for Hospital Management System cl 3150711 SE ae0120107530 1 Practical No. a Sequence Diagram S Aim: Draw a Sequence Diag; "6 f és wy - Mae Tam for selecteg pplication Exercise: TESTS APPOINTMENTS.y 30 201075 oot? Practical No, 7 Data Flow Diagram Draw a Data Flow Diagram for selected application Aim: Exercise: ta Flow Diagram for Hospital Management System Dai0 0753 1201 200 Practical No. 8 Function Point SL Olnt Apply FP oriented estimation Model for selected application Aim Exercise ly FP oriented estimation model for Hospital Management System Apply Hospiral Management Tacome gemmeat Systems — Finaace Masag 7 Expeeditare Consultantsgot 70107520 Aim: Study of vari, for selected applic; ; cation Sample Test Case s,, [Test Scenario 1D | Test Case Description Pre Requisite | Pre-Req tExecut S.No | Action Inputs Enter vad Email & incorrect password | en m™m