You are on page 1of 42

Online Hospital Management System

1. Introduction Title: Online Hospital Management System


1.1 Purpose
The Software is for the automation of Hospital Management. It maintains two levels of users:1. Administrator Level 2. User Level The Software includes: Maintaining Patient details. Providing Prescription, Precautions and Diet advice. Providing and maintaining all kinds of tests for a patient. Billing and Report generation.

1.2 Scope
Patient registration Appointments scheduling Billing and payments (cash, CC, insurance) Security of the whole system Pharmaceutical drugs/equipment Staff management (work roster, availability, scheduling, etc.) Management functions (report generation, accounting, etc.) System administration Resource allocation (booking rooms, operating theatres, etc.) Comprehensive database Web interface (proposed for future)

1.3 Definitions, Acronyms, and Abbreviations.


Problems with conventional system Lack of immediate retrievals: The information is very difficult to retrieve and to find particular information like- E.g. - To find out about the patients history, the user has to go through various registers. This results in inconvenience and wastage of time.

1.

2. Lack of immediate information storage: The information generated by various transactions takes time and efforts to be stored at right place. A.I.T.S. Rajkot 1

Online Hospital Management System

3. Lack of prompt updating: Various changes to information like patient details or immunization details of child are difficult to make as paper work is involved. 4. Error prone manual calculation: Manual calculations are error prone and take a lot of time this may result in incorrect information. For example: calculation of patients bill based on various treatments. 5. Preparation of accurate and prompt reports: This becomes a difficult task as information is difficult to collect from various registers.

1.4 References
Books Black Book ASP .NET Master in ASP .Net Master in SQL Server 2008 Murachs SQL Server 2008 for developers Professional ADV.NET 2.0 -Wrox Publication. Asp.net 4, unleashed Pearson Publication

Websites www.Bazee.com www.WikiPedia.com www.Online Auctionworld .com www.google.com www.ebay.com www.onlineauction.com www.bidjeeto.com

1.5 Overview

A.I.T.S. Rajkot

Online Hospital Management System Project is related to Hospital Management System. The project maintains two levels of users:Administrator Level-Doctor User Level-Data Entry Operator Main facilities available in this project are:1. Maintaining records of indoor/outdoor patients. 2. Maintaining patients diagnosis details, advised tests to be done. 3. Providing different test facilities to a doctor for diagnosis of patients. X-Ray Urine Test Stool Test Sonography Test Gastroscopy Test Colonoscopy Test Blood Test Biochemistry Test Maintaining patients injection entry records. 5.Maintaining patients prescription, medicine and diet advice details. 6.Providing billing details for indoor/outdoor patients. 7.Maintaining backup of (betweenmentioned dates). data as per user requirements.

8.If user forgets his/her password then it can be retrieved by question.

hint

9.In this project collection of data is from different pathology labs. 10.Results of tests, prescription, precautions and diet advice will be automatically updated in the database. 11.Related test reports, patient details report, prescription and billing reports can be generated as per user requirements. 12.User or Administrator can search a patients record by his/her name or their registration date. 13.Patients diet advice can be provided in Hindi.

A.I.T.S. Rajkot

Online Hospital Management System

2. The Overall Description 2.1 Product Perspective


The product requires a browser .It will support IE 5.0+, NetScape 4+, Mozilla 1+, and Opera. External interfaces include keyboard and mouse, enabling navigation across screens and Internet Connection if Possible. 2.1.1 Interfaces Input from the user will be via keyboard input and mouse point and click. Theuser will navigate through the software by clicking on icons and links. The icons will give appropriate responses to the given input. 2.1.2 Hardware Interfaces

MICROPROCESSOR

INTEL PENTIUM IV OR HIGHER

SYSTEM BUS SPEED

533 MHz

PROCESSOR SPEED

2.0 GHz

MAIN MEMORY

256 MB

SECONDARY MEMORY

40 GB

SECONDARY MEMORY SPEED

270 MHz

2.1.3 Software Interfaces

OPERATING SYSTEM

WINDOWS XP/2000,SERVER,Windows 7

WEB SERVER A.I.T.S. Rajkot

IIS (Internet Information Server) 4

Online Hospital Management System

WEB SERVER DESIGNING TOOL

ASP.Net,.NetFramework 3.5v

LANGUAGE

C#

DATABASE

MS-SQL SERVER 2008

Front-end and back-end selection An important issue for the development of a project is the selection of suitable front-end and back-end. When we decided to develop the project we went through an extensive study to determine the most suitable platform that suits the needs of the organization as well as helps in development of the project. The aspects of our study included the following factors. Front-end selection: 1. It must have a graphical user interface that assists employees that are not from ITbackground. 2. Scalability and extensibility. 3. Flexibility. 4. Robustness. 5. According to the organization requirement and the culture. 6. Must provide excellent reporting features with good printing support. 7. Platform independent. 8. Easy to debug and maintain. 9. Event driven programming facility. 10.Front end must support some popular back end like Ms Access. According to the above stated features we selected VS10.0 as the front-end for developing our project. Back-end Selection: 1. Multiple user support. 2. Efficient data handling. 3. Provide inherent features for security. 4. Efficient data retrieval and maintenance. 5. Stored procedures. 6. Popularity. 7. Operating System compatible. 8. Easy to install. 9. Various drivers must be available. 10.Easy to implant with the Front-end. According to above stated features we selected Ms-Access as the backend. A.I.T.S. Rajkot 5

Online Hospital Management System The technical feasibility is frequently the most difficult area encountered at this stage. It is essential that the process of analysis and definition be conducted in parallel with an assessment to technical feasibility. It centers on the existing computer system (hardware, software etc.) and to what extent it can support the proposed system.

2.1.4Communications Interfaces Local Area Network, which is internal to LCHP, used for communication among employees & HRM. 2.1.5 Memory Constraints Memory size required depends on number of employee records and Datas. 2.1.6 Operations It is mainly related to human organizations and political aspects. The points to be considered are: What changes will be brought with the system? What organization structures are disturbed? What new skills will be required? Do the existing staff members have these skills? If not, can they be trained in due course of time? The system is operationally feasible as it very easy for the End users to operate it. It only needs basic information about Windows platform.

2.2 Product Functions


The system functions can be described as follows: 1. Registration: When a patient is admitted, the front-desk staff checks to see if the patient is already registered with the hospital. If he is, his/her Personal Health Number (PHN) is entered into the computer. Otherwise a new Personal Health Number is given to this patient. The patients information such as date of birth, address and telephone number is also entered into computer system. 2. Consultation: The patient goes to consultation-desk to explain his/her condition so that the consulting nurse can determine what kind of ward and bed should be assigned to him/her. There are two possible circumstances: A.I.T.S. Rajkot 6

Online Hospital Management System a) If there is a bed then the patient will be sent to the bed to wait for the doctor to come. b) If there is no bed, the patient is put on a waiting list until a bed becomes available. 3. Patient check out. If a patient checks out, the administrative staff shall delete his PHN from the system and the just evacuated bed is included in available-beds list. 4. Report Generation: The system generates reports on the following information: patients, bed availability and staff schedules after every six hours. It prints out all the information on who has used which bed, when and the doctor that is taking care of a given patient as well as expected medical expenses.

2.3 User Characteristics


The system will be used in the hospital. The administrators, doctors, nurses and front-desk staff will be the main users. Given the condition that not all the users are computer-literate. Some users may have to be trained on using the system. The system is also designed to be userfriendly. It uses a Graphical User Interface (GUI). Front-desk staff: They all have general reception and secretarial duties. Every staff has some basiccomputer training. They are responsible for patients checkin or notification of appropriate people (e.g. notify administrator or nurse when an event occurs). Administrators: They all have post-secondary education relating to general business administration practices. Everyadministrator has basic computer training. They are responsible for all of the scheduling and updating day/night employee shifts. Administrators in the wards are responsible for assigning doctors and nurses to patients. Nurses: All nurses have post-secondary education in nursing. Some nurses are computer literate. Consulting nurses to whom patients give short descriptions of their conditions are also responsible for assigning patients to appropriate wards if the beds are available, otherwise putting patients on the waiting list. Nurses in wards will use the HPMS to check their patient list. Doctors:

A.I.T.S. Rajkot

Online Hospital Management System All doctors have a medical degree. Some have further specialized training and are computer literate. Doctors will use the HPMS to check their patients list.

2.4 Constraints
The constraint associated in the development of any software system includes those that are common to all system. The common constraints Some of the constraints are listed below with which we have developed this system. It requires Microsoft windows XP or ASP .Net Microsoft SQL server 2000 is required. User mistake can be turned into the improper answer. It is Hospital Management System and there is unique form layout and the report format. The common constraints may include lack of managerial participation tighter development schedule frequently working for management etc. It has some specification need: to run this software because is developed in the ASP.Net

2.5 Assumptions and Dependencies


Patient provides CC/insurance details when registering Appointments can be cancelled 24 hours in advance without penalty Patient medical history can be viewed by concerned doctors at the hospital with approval of the patient. Hospital is covered by insurance policy. Staff are assigned roles to interact with the system Staff have basic computer operating skills.

It is assumed that one hundred IBM compatible computers will be available before the system is installed and tested. It is assumed that the Hospital will have enough trained staff to take care of the system

2.6 Apportioning of Requirements.


The Website requires a browser. If any add-on or service like flash player missing error etc. occurs then website opens in a compatible view which gives error on the page. The browser requires the flash player to run flash objects if not possible then it provides a direct link to the flash player download link or any other plug in missing the it provides the interface to resolve the problem externally.

A.I.T.S. Rajkot

Online Hospital Management System

3. Specific Requirements
3.1 External Interfaces
Input from the user will be via keyboard input and mouse point and click. The user will navigate through the software by clicking on icons and links. The icons will give appropriate responses to the given input User interface: Main interface of HMS is a GUI window linked to different Functions such as to retrieve option that performs search for Staff Or Patient datas in database and return relevant records. Software interface : S/W Name : SQL server. Version: 8i Vendor: Microsoft Corp. External: server system. Hardware interface: Workstations: Personal computers used by employees in LCHP.

Memory constraints: Memory size required depends on number of employee records/Datas.

Communication interface : Local Area Network, which is internal to LCHP, used for communication among employees & HRM.

3.2 Functions
User side Section 1: Home Page Hospital startup details. Section 2: About Us Page Detailed description about Hospital A.I.T.S. Rajkot 9

Online Hospital Management System

Section 3: Facilities Detailed description Vision of Hospital Section 4: Registration form Registration form for patient, doctor, appointment Section 5: User Login Doctor Creating login sessions for the authorized user It will provide following sections to access it o Profile o Patient list o Patient profile list o Patient message o Patient prescription details and charge Patient Creating login sessions for the authorized user It will provide following sections to access it o Profile o Des. list o Solutions list o message

Admin side Section 1: Dashboard All latest statistics, total users, total users scheme showed, total user awaiting verification, total users awaiting activation, complaint status and complaint verification. Section 2: Verification Show all unverified users, show all unverified user, either edit, delete or activate either edit, delete or activate a user.

A.I.T.S. Rajkot

10

Online Hospital Management System Section 3: Management Users Show all users, search through parameters: name, user id etc.. Appointment list Show all scheme list, search through parameters: upload date, category, etc. Categories (Doctors, Patients) Add, edit, delete, activate, and deactivate a category. CMS Add, edit, and delete new static content. Like about us, history, T&C, logo etc. Section 4: Flag Reports Show all Query and data upload reports, view query reports, edit contents with reports, delete contents report. Section 5: Configurations & Settings Setup global parameters like: daily max user access for specific data for a specific scheme query, daily max scheme reviews, SEO meta tags, daily download, Limit for a user, manage other rules for comments and ratings, etc.

3.3 Performance Requirements


The performance of our product is at its best if stored locally, as the response time will be much faster. If the product accessed via Internet, the performance is limited by the connection speed. The only foreseen limitation is that of web-server response. Response Time The system shall give responses in 1 second after checking the patients information. Capacity The System must support 1000 people at a time. User-interface The user-interface screen shall respond within 5 seconds. Conformity The systems must conform to the Microsoft Accessibility guidelines

3.4 Logical Database Requirements


Directory Structure of HMS 1. ASP.net
FORM

A.I.T.S. Rajkot

11

Online Hospital Management System


frmBill frmDivisionMaster frmDoctorMaster frmDoctorQualificationMaster frmDoctorSpecialistMaster frmDoctorTypeMaster frmDoctorVisitChargeMaster frmDoctorVisitTypeMaster frmLogin frmPrimaryChargeGroup frmPrimarySubChargeGroup frmRegistration frmRoomTypeMaster frmTreatment frmUserDetail frmUserPermission MODULE ModHMS CLASS clsHMS REPORT CrpChargeMaster. CrpDailyCollection CrpDepositeDetailDateWise CrpDoctorMasterReport CrpDoctorWiseCaseReport CrpPatientVisitReport CrprptDepoitdetailRegIdWise CrprptReliefReport CryrptIPDBillDetail CryrptOPDBillReport

2. SQL 2000
DATA dbHMS_Data LOG dbHMS_Log SQL CreateTable uspSaveDrMaster. uspSaveUserDetail

A.I.T.S. Rajkot

12

Online Hospital Management System


uspSaveTreatmentDetail uspSaveRoomType uspSavePrimarySubChargeGroup uspSavePrimaryChargeGroup uspsavePatientMaster uspSaveDrVisitType uspSaveDrVisitCharge uspSaveDrType uspSaveDrSpecialist uspSaveDrQualification uspTotalBill uspSaveDivisionMaster uspSaveBillDetail uspDrMasterNavigation uspBillDetailNevigation uspRegistrationNevigation uspTreatmentNavigation uspRptReliefReport uspRptPatientWisecaseReport uspRptOPDBillReport uspRptOPDBillReport uspRptDoctorWiseCaseRepot uspRptDoctorChargeReport. uspRptDepositDetailReport uspRptDailyCollectionReport uspRptChargeMaster uspOPDBillReport

DATABASE TABLES

dbHMS Login DivisionMaster PrimaryChargeGroup PrimarySubChargeGroup DrType DrQualification DrSpecialist DrMaster DrInsentive DrVisitType RoomType DrVisitCharge PatientMaster MLCDetail DepositDetail DetailOfShifting

A.I.T.S. Rajkot

13

Online Hospital Management System


TreatmentDetail BillDetail Form

Table No Name Field Name DivId DivDescri ption Table No Name Field Name DivId

:1 : DivisionMaster Data Type SmallI nt Varch ar :2 : PrimaryChargeGroup Data Type SmallInt Description Division Name Automatical ly Genetated Primary Charge Group Description Validation Foreign Key From DivMaster Primary Key Description Automatically Genetated Division Name Validation Primary Key If not then null.

PriGroupId

SmallInt

PriGroupDescr iption

Varchar

If not null.

then

Table No Name Field Name PriGroupId

:3 : PrimarySubChargeGroup Data Type SmallInt Description Primary Group Id Validation Foreign Key From PriGroupMas ter Primary Key If not then null. If not then 14

PriSubGroupId ChargeDescript ion ChargeAmt A.I.T.S. Rajkot

SmallInt Varchar

Numeric

Automatically Genetated Primary Sub Charge Description Charge

Online Hospital Management System Amount Charge Apply To null. If not then null.

ApplyTo

Varchar

Table No Name Field Name DrTypeId DrTypeD escri Table No Name Field Name DrQualiId DrQualiD escri

:4 : DrType Data Type SmallInt Varchar Description Automatically Genetated Doctor Type Description Validation Primary Key If not then Null.

:5 : DrQualification Data Type SmallInt Varchar Description Automatically Genetated Doctor Qualification Description Validation Primary Key If not then Null.

Table No Name Field Name DrQualiI d Specialist Id SpecDesc ri Table No Name Field Name DrVisitTyp eId DrVisitDes cri

:6 : DrSpecialist Data Type SmallInt SmallInt Varchar Description Doctor Qualification Id Automatically Genetated Doctor Specialist Description Validation If not then Null. Primary Key If not then Null.

:7 : DrVisitType Data Type SmallIn t Varchar Description Automatically Genetated Doctor Visit Description Validation Primary Key If not then Null. 15

A.I.T.S. Rajkot

Online Hospital Management System

Table No Name Field Name DrTypeId DrVisitType Id RoomTypeI d DrCharge Table No Name Field Name RoomTypeI d RoomType Descri PtRoomCh arge AdvanceDe posite

:8 : DrVisitCharge Data Type SmallInt SmallInt SmallInt SmallInt :9 : RoomType Data Type SmallInt Varchar SmallInt SmallInt Description Automatically Genetated Room Type Description Patient Room Charge Advanced Deposite Validation Primary Key If not then Null. If not then Null. If not then Null. Description Doctor Type Id Doctor Visit Type Id Room Type Id Doctor charge Validation Foreign Key from DrType Foreign Key from DrVisitType Foreign Key from RoomType If not then Null.

Table No Name Field Name RegType RegId RegDate PName PAddr1 PAddr2

: 10 : PatientMaster Data Type Varchar SmallInt Datetime Varchar Varchar Varchar Description Registration Type Automatically Genetated Registration Date Patient Name Patient Address1 Patient Validation It must be enterd. Primary Key It must be enterd. It must be enterd. It must be enterd. If not then Null. 16

A.I.T.S. Rajkot

Online Hospital Management System Address2 Patient BirthDate Patient Age Patient Sex Patient Phone No Patient Mobile No Consultant Doctor Id Reference Doctor Name Patient Mediclaim

PBirthdate Age Sex Phone Mobile ConsDrId RefDrNam e Mediclaim

Datetime SmallInt Varchar Varchar Varchar SmallInt Varchar Varchar

If not then Null. If not then Null. It must be enterd. If not then Null. If not then Null. If not then Null. If not then Null. It must be enterd.

Table No Name Field Name RegId MLCAdmiD ate

: 11 : MLCDetail Data Type SmallInt Datetime Description Ledger Id MLC Patient Admit Date Case No MLC Date Time Informed to Police Police sub Officer Name Buccle No Name of Police Station Time Arrived MLC Patient DisChargeD ate Validation Foreign Key from PatientMaster If not then Null.

CaseNo MLCDate TimeInforme d PSOName

SmallInt Datetime Datetime

If not then Null. If not then Null. If not then Null.

varchar

If not then Null.

BucNo PoliceSt

SmallInt varchar

If not then Null. If not then Null.

TimeArrived MLCDischar geDate

Datetime Datetime

If not then Null. If not then Null.

A.I.T.S. Rajkot

17

Online Hospital Management System

Table No Name Field Name RegId ReceiptNo ReceiptDate Amount UserId

: 12 : DepositDetail Data Type SmallInt SmallInt datetime Integer SmallInt Description Registration Id Automatically Genetated Reciept Date Deposite Amount User Id Validation Primary Key. Primary Key If not then Null. If not then Null. If not then Null.

Table No Name Field Name ShiftingId RegId RoomTypeI d RoomNo Bed No FromDate ToDate Table No Name Field Name DrId DrName DrNickNa me Address1

: 13 : DetailOfShifting Data Type smallint smallint smallint smallint smallint Datetime Datetime : 14 : DrMaster Data Type smallInt Varchar Varchar Varchar Description Automatically Genetated Doctor Name Doctor Nick Name Doctor Address 1 Validation Primary Key It cannot be Null. It must be enterd. It cannot be Null. 18 Description Automatically Genetated Automatically Genetated Room Type Id Room No Bed No From Date To Date Validation Primary Key Primary Key If not then null. If not then null. If not then null. If not then null. If not then null.

A.I.T.S. Rajkot

Online Hospital Management System Address2 PhoneNo MobileNo QualiId DrTypeId SpecialistI d DivId ConsultCh arge FollowUp Charge CaseValid UpTo Insentive BasicSalar y Varchar Varchar Varchar Varchar Integer smallInt smallInt smallInt smallInt smallInt smallInt Numeric Doctor Address 2 Phone Number Mobile Number Qualifiction Id Doctor Type Id Specialist Id Division Id Consultant Charge Follow Up Charge Case Valid Up To Insentive Doctor Basic Salary If not then null. It cannot be Null. If not then null. If not then null. If not then null. If not then null. If not then null. If not then null. If not then null. If not then null. If not then null. If not then null.

Table No Name Field Name DrId PriGroupI d PriSubGr oupId Insentive Type

: 15 : DrInsentive Data Type smallint Smallint Smallint Description Doctor Id Primary Charge Group Id Primary subCharge Group Id Percentge Of Insentive Type % or / Validation If not then null. If not then null. If not then null.

Smallint Varchar

If not then null. If not then null.

Table No Name Field Name RegId TreatId

: 16 : TreatmentDetail Data Type Small Int Small Int Description Registration Id Automatically Genetated Validation Primary Key Primary Key 19

A.I.T.S. Rajkot

Online Hospital Management System TreatDate DrId PriGroupId Dateti me Small Int Small Int Small Int Small Int Small Int Small Int Treatment Date Doctor Id Primary Charge Group Id Primary Sub Charge Group Id Treatment Charge Amount Quantity Total Amount If not then null. Foreign Key From DrMastrer Foreign Key From PriGroupMaster Foreign Key From PriSubGroupMaster If not then null.

PriSubGroupId

ChargeAmt

Qty TotalAmount

If not then null. If not then null.

Table No Name Field Name RegId Bill No Bill Date

: 17 : Bill Detail Data Type SmallInt SmallInt Datetime Varchar Varchar Datetime Integer Integer Integer Integer Integer Varchar Integer Integer Description Register Id Patient Bill No Bill Date Bill Type DisCharge Type DisCharge Date Total Bill Amount Nurshing Charge Percentage Nurshing Charge Amount Other Charges Relief Amount Remark Of Relief Service Tax Percentage Service Tax Validation It must be entered. Primary Key It must be entered. If not then Null. If not then Null. It must be entered. If not then Null. If not then Null. If not then Null. If not then Null. If not then Null. If not then Null. If not then Null. If not then Null. 20

Bill Type DischargeTyp e DischargeDate TotalBillAmt NurChargePer NurChargeAm t OtherCharge ReliefAmt RemarkOfReli ef SerTaxPer SerTaxAmt A.I.T.S. Rajkot

Online Hospital Management System Amount Total Deposite Net Payable Amount Payment Mode Remark Of Payment

TotalDepositA mt NetPayable PayMode RemarkOfPay ment Table No Name Field Name UserId : 18

Integer Integer Varchar Varchar

If not then Null. If not then Null. If not then Null. If not then Null.

: UserDetail Data Type SmallInt Description Automatical ly Genetated User Name User Address User Contact No User Permission Validation Primary Key

UserName UserAddr ContactNo Permission

Varchar Varchar Varchar Varchar

If not then null. If not then null. If not then null. If not then null.

Table No Name Field Name UserId UserPasswd LoginDate LogoutDate

: 19 : Login Data Type SmallInt binary Datetime Datetime Descriptio n User Id User Password User Login Date User Logout Date Validation Foreign Key From UserDetail If not then null. If not then null. If not then null.

Table No Name Field Name FormId

: 20 : Form Data Type SmallInt Description Form Id Validation If not then null. 21

A.I.T.S. Rajkot

Online Hospital Management System FormNam e Varchar Form Name If not then null.

3.5 Design Constraints


Must use a SQL based database. SQL standard is the most widely used database format.Restricting to SQL allows easy of use and compatibility for Web Store. Compatibility is only tested and verified for Microsoft Internet Explorer version 6 and 7. Other versions may not be 100% compatible. Alsoother browsers such as Mozilla or Firefox may not be 100% compatible.

Database The system shall use the MySQL Database, which is open source and free. Operating System The Development environment shall be Windows 2000. Web-Based The system shall be a Web-based application.

3.5.1 Standards Compliance Report Format: IEEE Format Data Naming: Some general comments about the structure of entity and attribute names; names must be: meaningful; self-documenting derived from the business use or purpose; and repeatable (different people from different areas of the ministry reading the name at different times must have the same understanding of what the name means -- a corporate-wide use of the name). Accounting procedures: The customer needs to enter its credit card information for purchasing any items or products. They are to be securely maintained so that they can ensure his privacy. The account information is sent for the transaction process so that the process continues while purchasing. A.I.T.S. Rajkot 22

Online Hospital Management System

3.6 Software System Attributes


3.6.1 Reliability The reliability of the proposed system will be high due to the above stated reasons. The reason for the increased reliability of the system is that now there would be proper storage of information. 3.6.2 Availability
The system should be available at all times, meaning the user can access it using a web browser, only restricted by the down time of the server on which the system runs. In case of a of a hardware failure or database corruption, a replacement page will be shown. Also in case of a hardware failure or database corruption, backups of the database should be retrieved from the server and saved by the administrator. Then the service will be restarted.

3.6.3 Security Each member is required to enter an individual password when accessing the site. Administrators have the option of increasing the level of password security their members must use. The data on your site is secured through multiple layers of protection. One of those security layers involves member passwords. For maximum security of your site, each member must protect their password. Patient Identification The system requires the patient to identify himself /herself using PHN Logon ID Any user who uses the system shall have a Logon ID and Password. Modification Any modification (insert, delete, update) for the Database shall be synchronized and done only by the administrator in the ward. Compliance The system must comply with the Regional Health Authority Regulations concerning privacy, section 703.2RHA/2000/v78 Front Desk staff Rights Front Desk staff shall be able to view all information in A.I.T.S. Rajkot 23

Online Hospital Management System HPMS, add new patients to HPMS but shall not be able to modify any information in it. Administrators' Rights Administrators shall be able to view and modify all information in HPMS Nurses' Rights Nurses shall only be able to view all information in HPMS. Doctors Rights Doctors shall only be able to view all information in HPMS 3.6.4 Maintainability Back Up The system shall provide the capability to back-up the Data Errors The system shall keep a log of all the errors.

3.6.5 Portability
The application is ASP.Net based and should be compatible with all other systems which have a ASP implementation. The end-user part is fully portable and any system using any web browser should be able to use the features of the application, including any hardware platform that is available or will be available in the future.

3.7 Organizing the Specific Requirements

3.7.1 System Mode

A.I.T.S. Rajkot

24

Online Hospital Management System

A.I.T.S. Rajkot

25

Online Hospital Management System 3.7.2 User Class

Class Diagram 1

A.I.T.S. Rajkot

26

Online Hospital Management System

ClassDiagram 2

3.7.3 Objects
Helpdesk Patient Registration and Appointment Scheduling Module Outpatient Management Module Doctors workbench/ CPOE Inpatient and Ward Management Patient Billing & Insurance Module Pharmacy Module General Stores/ Inventory Laboratory Information System Radiology Management Module Electronic Medical Record (EMR) Dietary Module

A.I.T.S. Rajkot

27

Online Hospital Management System


House Keeping Module Nursing Module Emergency Management Machine Maintenance CSSD Blood Bank Financial Accounting Module Fixed Asset Module Payroll Module MIS Dashboard Services Module User Manager Module (security workflow)

3.7.4 Functional Hierarchy One of the tools of the tructure analysis is the Data flow Diagram. A DFD is a graphical representation of the system. The data flow Diagram is used by the System analysis to explain the flow of the data in the system. A DFD uses Some Elements as its building blocks. The following is a brief description of these elements. External Entity

The external entityis a source and/or destination of the data for the system.As the name suggest,it lies outside the context of the system.It is represented by solid rectangles.

Process

A process represent some amount of word beging performed on the data.A process does transformation of the data from one form to another. A circle represent a process.The process must be named and numbered appropriately.

Data Flow

A data flow designate an interface among different component in the DFD.It represent the path of data as it flow through the system. An arrow represent a data flow.The name of the data flow is written along the line.

A.I.T.S. Rajkot

28

Online Hospital Management System

Data Source

A data source is a repository of data. An open ended rectangle or tow horizontal parallel lines represent it.

A DFD,whichdesribes the system at a very general level,is called the context diagram. It contains a single process,but it plays a vary important role in studying the system. The following pages displayed the context diagram and the DFDs of the subsequent level of the Front Desk,Room Service & Restaurant.

A.I.T.S. Rajkot

29

Online Hospital Management System


DEPOSIT RECEIPT DETAIL DEPOSIT PAYMENT DETAIL REGISTRATION DETAIL RECEIVE FILE PATIENT RECEIVE TREATMENT DETAIL BILL DETAIL TREATMENT SERVICE DETAIL DOCTOR GIVE SALARY DETAIL

HOSPITAL MANAGEMENT SYSTEM

PAYMENT DEATIL REQUEST FOR RELIEF REVEIVE RELIEF REPORT REQUEST FOR RELIEF GIVE RELIEF DETAIIL

MANAGEMENT

Context Level Diagram

A.I.T.S. Rajkot

30

Online Hospital Management System

PATIENT

DOCTOR

TREATMENT DETAIL

7.0 REPORT

Patient Master REG.ID, DETAIL

PATIENT DETAIL

REG ID. DETAIL

TREATMENT DETAIL TREAT TREATMENT DETAIL BILL NO REPORT

REG.ID, DETAIL

1.0 REGISTRATIO N

REG ID.

2.0 TREATMENT

REG ID, TREAT ID

5.0 BILL

MANAGEMENT

RED ID , SHIFTING ID IPD REG ID IPD REG ID PATIENT DETAIL PATIENT DETAIL DEPOSITE DETAIL

BILL DETAIL REQUEST RELIEF DETAIL

SEND RELIEF

3.0 SHIFTING

4.0 DEPOSITE DEPOSITE DETAIL PAY BILL AMOUNT

6.0 RELIEF

SH D IFT ET I A NG IL

REG ID , RECEIPT NO REG ID , RECEIPT NO PAY DEPOSIT

BILL NO , DETAIL REQUEST RELIEF PATIENT RECEIVE RELIEF

SHIFTING DETAIL

First Level Diagram

A.I.T.S. Rajkot

31

Online Hospital Management System

PATIENT MASTER

REG ID,DETAIL OPD DETAIL

REG ID

PATIENT DETAIL PATIENT REGID , DETAIL

1.1 PATIENT DETAIL & REG TYPE

REG ID

1.2 CHECK REG TYPE

IPD

1.3 TAKE MLC DETAIL

DETAIL

MLC DETAIL

Fir :- Second Level DFD for Registration

SECOND LEVEL DFD FOR REGISTRATION

A.I.T.S. Rajkot

32

Online Hospital Management System

SECOND LEVEL DFD FOR TREATEMENT

PROCESS

A.I.T.S. Rajkot

33

Online Hospital Management System

REG ID PATIENT

3.1 VERIFY REG TYPE

IF IPD

IF EXIST

3.3 ALLOCATE ROOM

3.2 CHECK ROOM AVAILABLE

RED ID & DETAIL

DETAIL OF SHIFTING

Second Level DFD for Shifting

SECOND LEVEL DFD FOR SHIFTING

A.I.T.S. Rajkot

34

Online Hospital Management System

DEPOSITE

DETAIL

REG ID PATIENT

4.1 PAY DEPOSIT


MANAGEMENT REG ID,DEATIL

RECEIPT SEND REPORT

4.2 GENERATE REPORT

Second Level DFD for Deposit SECOND LEVEL DFD FOR DEPOSIT

A.I.T.S. Rajkot

35

Online Hospital Management System

5.1.1 CALCULATE TREATMENT CHARGES


TOTAL CHARGE

BILL DEATIL

5.1.2 CALCULATE SHIFTING CHARGES


TOTAL CHARGE REG ID

REG ID

PATIENT BILL DETAIL

5.1 BILL GENERATION

REG ID DEDUCT RELIEF AMT

5.2 TOTAL RELIEF

REG ID TOTAL CHARGE TOTAL CHARGE REG ID

5.1.3 CALCULATE NURSING CHARGES

REPORT

5.1.2 CALCULATE OTHER CHARGES

MANAGEMENT

Second Level DFD for Bill Detail

SECOND LEVEL DFD FOR BILL

A.I.T.S. Rajkot

36

Online Hospital Management System

BILL DETAIL

RELIEF AMOUNT

PATIENT REQUEST RELIEF

6.0 RELIEF PROCESS

SEND INFORMATION MANAGEMENT RELEIF AMOUNT

Second Level DFD for Relief

SECOND LEVEL DFD FOR RELIEF

A.I.T.S. Rajkot

37

Online Hospital Management System

VARIOUS TRANSACTION REPORT TRANSACTION DETAIL

MANAGEMENT

7.1 VARIOUS REPORT


REQUEST REPORT MASTER DEATAIL VARIOUS MASTER

Second Level DFD for Report

3.8 Additional Comments


The website contains some extra or additional services like free hosting advertisements, flash files etc. are handled with the change management process which may discuss later. This website provides high portability thats why we can change or edit/remove any components from the site easily from server side.

4. Change Management Process


A.I.T.S. Rajkot 38

Online Hospital Management System

To incorporate ad hoc changes in the requirements and to see if proper changes to the system meet the requirements, change management process will be done iteratively with all the activities, the following strategy will be followed. The Developer will identify a new requirement or a modification in a requirement and communicate it to the team lead via email/Msg or to the entire team in a meeting. The Developer will assess the feasibility of the proposed change considering the time constraints and structural constraints of the implemented modules and develop an implementation strategy and submit it to the mentor for approval. A change plan will be created for the implementation of the change and following sequences of the changes is determined. The Developer will then continue implementing the new requirements. Then testing will be done on the new programmed system. During the testing phase, the product will be tested for satisfying the requested changes. After the changes have been done, update will be made to documentation also. The changes will then be verified for the last time, and a new system release is made.

5. Document Approvals
A.I.T.S. Rajkot 39

Online Hospital Management System

All the document of the Online Hospital Management are correct,Understandable and verified. All the things done in this document is legal ang in the guidance of Mr.Pinak Gosh.(prof. AITS). All the DFDs And Other Diagrams are as per the IEEE Standards. Hence the document is acceptable and correct. The document in this file is an annotated outline for specifying software requirements, adapted from the IEEE Guide to Software Requirements Specifications (Std 830-1993).

Approved by: Mr. Pinaki Gosh

Signature: ------------------------------------------

Date: ----------------------

A.I.T.S. Rajkot

40

Online Hospital Management System

6. Supporting Information Appendix:


SnapShots

Table of Contents
1. Introduction 1.1 Purpose 1.2 Scope 1.3 Definitions, Acronyms, and Abbreviations. 1.4 References 1.5 Overview 2. The Overall Description 2.1 Product Perspective 2.1.1 Interfaces 2.1.2 Hardware Interfaces 2.1.3 Software Interfaces 2.1.4 Communications Interfaces 2.1.5 Memory Constraints 2.1.6 Operations 2.2 Product Functions 2.3 User Characteristics 2.4 Constraints 2.5 Assumptions and Dependencies 2.6 Apportioning of Requirements. 3. Specific Requirements 3.1 External Interfaces 3.2 Functions 3.3 Performance Requirements 3.4 Logical Database Requirements 3.5 Design Constraints 3.5.1 Standards Compliance 3.6 Software System Attributes 3.6.1 Reliability 3.6.2 Availability 3.6.3 Security 3.6.4 Maintainability 3.6.5 Portability 1 1 1 1 2 2 4 4 4 4 4 6 6 6 6 7 8 8 8 9 9 9 11 11 22 22 23 23 23 23 24 24

A.I.T.S. Rajkot

41

Online Hospital Management System


3.7 Organizing the Specific Requirements 3.7.1 System Mode 3.7.2 User Class 3.7.3 Objects 3.7.4 Functional Hierarchy 3.8 Additional Comments 4. 5. 6. Change Management Process Document Approvals Supporting Information 24 24 26 27 28 38 38 39 41

A.I.T.S. Rajkot

42