The Well Meadows Hospital Management System

The Well Meadows Hospital Management SystemThis document describes an online worry arranging for a sm all(prenominal) infirmary phoned as wellmeadows. This form creates online entropy computer storage for all the breeding related to the proceedings of the hospital and whence making the cultivation available as well as more reliable to the users. The information becomes easily recoverible as well as more secure with the trunk being secured by user credentials.The hospitals ongoing functionality is based on a register based system that involves the affirming of e very(prenominal) transaction, records of unhurrieds, doctors, c atomic number 18 fors in huge files that ar stored in hospitals store room. It is not only problematical to search for certain information only likewise very difficult to maintain historical selective information. The old files are prone to get damaged and it is very difficult to manage this huge collection of documents and keep it organized.Th e new system is based on a entropybase centering system that allows secure, easy and reliable storage of data and convalescence is as well very easy. In the old system, a user needed to k today in which register particular information is stored but in the new system a user has a graphical interface, where he arsehole merely search for the information by doing some clicks and selecting the flush options (Liang 2010). The ease in admission chargeing information not only improves the information instruction but also impacts the day to day activities of the hospital. It reduces the delay in information retrieval and the delay in providing necessary treatment to the long-sufferings as per their historic records is also reduced that leave improve the efficiency and effectiveness of the treatment (Prokosch Dudeck 1995).Intended audition and Reading SuggestionsThis document is meant for the users of the system i.e. the administrators and cater of the wellmeadows hospital. Thi s document explains the system design and its usage and not meant for external users. This document not only guides the user how to locomote the system but also tells how to use the system efficiently to match with requirements of the user and let him take the profit out of it. This document provide also wait on the developers in the situation where modifications are required in the system.Project ScopeThe project currently is restrain to the internal use of the hospital and is simply meant to store and provide utilizable information. The system doesnt generate whatsoever information or predictions of its own. The system will be helpful in better counselling of the hospital and will provide all the information in an organized manner. This project is not meant for users outside(a) the hospital and will not allow each person outside the hospital to see the internal and personal information of the people connected to the system. The system will keep the information secure and will keep it limited to people with proper(a) access only.Overall DescriptionProduct PerspectiveThis product is a change of methodology for the hospitals and firstly, it will be implemented in the Wellmeadows hospital. There are several similar systems in other big hospitals but this system is designed to meet the cost and advantage requirements of the small hospital. This product is an evolutionary product that will be improved in the future and more functionality will be added to it.Product FeaturesThe product is useful to the hospital in a number of ways as it provides following features to the hospital-Easy, storage and retrieval of all uncomplainings information that not only helps to maintain track record but also helps the doctors as they can know the treatment history of the patients.Store the entire information about doctors that allow the hospital to decide, which patient will be treated by which doctor. This product not only helps in providing better treatment to the p atients but also helps in mental synthesis trust with patients. It also helps to know about the doctors, who are preferred by patients (Sumathi Esakkirajan 2007).Storage of staffs information that helps in smooth running of the hospital.Storage of all drugs utilize in the hospital and all drugs being prescribed to the patients that allows more control all over the quality of drugs used. It also ensures uniformity among variant doctors and to maintain the stock of drugs as per their requirements (Sumathi Esakkirajan 2007).User Classes and CharacteristicsThe system will be used by internal users only and will be accessible to outside users in a limited form. Following are the users of the system Hospital receptionists The hospital receptionist will act as system administrators and will make all the entries in the system. They will gain access to all the information in system and will take control of the normal proceedings of the hospital. Receptionists will register the patien ts, allocate staff to versatile wards, give appointments to patients and will maintain the central stock of medicines and drugs.Charge Nurses The charge nurses will manipulate the information related to their specific ward and will be able to see all patients information in their ward and provide medication accordingly. They will also be able to see which staff is on duty in their ward and also will be able to see the stock of medicines in their ward.Consultants The consultants will able to see the patients information and the incline of appointments that drive been allocated to them. The will be also able to see the wards in which they are assigned duties and will also be able to prescribe medicines to their patients. uncomplainings Patients will be able to see the appointments they have in the hospital and will be able to see the medicines that have been prescribed to them from the system.Operating EnvironmentThe system will be a web based system and can be accessed within a nd outside the hospital through a link over hospitals website. The users will login the system utilize a username and war cry that will be provided to them by the system administrator and the system will be independent of the run system.Assumptions and DependenciesThe system assumes that the information being added to the system is correct and authenticated. It is also assumed that the username and give-and-take will be kept secret and will not be shared with anyone. The users will be themselves responsible for losing passwords. This system doesnt include a mailing feature and hence the user should not lose their passwords in any case. The passwords will have to be reset by the database administrator only.System FlowA data give ear diagram as its name suggests represents the string up of data in any system. There is a huge flow of data and information in any information system. This flow is analyzed with the help of data flow diagrams. information flow diagrams can be used f or visualization of data work outing. On a DFD, data items flow from an external data seed or an internal data store to an internal data store or an external data sink via an internal serve up (Calmet Pfalzgraf 1996). A data flow diagram is composed of several components Entities Entities are the sources of information in any system. These entities are the external sources of information in any system. It is very important to mention all the entities in a system. This ensures the proper flow of information in a system. These also act as external sinks for the system (Dennis, Wixom Roth 2006).Database or data store A database stores the information in any system. These act as internal data sources for a system. It stores the information from one process and provides information to other processes. It also acts as internal sinks in the system.Processes A process is a function performed by the system. Each process helps to access the information from database or an entity and p rovide the information back to the entity or database (Dennis, Wixom Roth 2006).The DFDs are represented in several levels. With increase in each level the details in the diagram also increased. Level-0 would contain minimum details, while level 1 would contain more details than level 0 and so on.This section explains flow of the system, how the system operates and its functionalities with the help of data flow diagrams. The level of details increases with each diagram. The system at the highest level is nothing but a hospital management system the inner details are not specified in the data flow diagram level-0 (Johns 2002). Here is the zero level data flow diagram (DFD level 0)The above diagram shows the four entities that will be conglomerate in the system- patients, doctors, hospital staff and nurses. These are the four main sources of information in the system.As the system is broken down into several modules, these entities match up their desired roles (Johns 2002). This bre akdown gives us the exact information about the operations performed by the system and the entities involved in each operation.(DFD level1)In the DFD level -1, the system is divided into three major domains namely patient management system, stock management system and staff management system. Patient management system is related to patients that includes two types of patients- inpatients and outpatients. Inpatients are those, which get admitted in the hospital and put up there while the outpatients take appointments and visit the hospital at given date and while (Johns 2002).The second major section of the system is stock management system. In this, the requirements of the hospital are analyzed and accomplished such as clinical and non clinical requirements like drugs, bandages and other requirements. This part also maintains the division of these items among various wards and among various departments of the hospital.The third section of the system is about the staff al localisa tion principle system that ensures that all staff is being assigned proper duties and each wards acquire proper number of employees and nurses for its daily operations and also for emergency situations. It also ensures that the consultants are visiting the wards on time and each patient is getting proper attention.External Interface RequirementsUser InterfacesThe user interface is simply a web interface, which is presented to the user through a web browser. This allows user to enter data and select from various drop down menus. These drop down menus show the content read from the database. By simply clicking to submit buttons, user can survive data into database. The user interfaces will also implement checks for null values being entered into database (Galitz 2009). It displays the format for date values to be entered, but doesnt validate them. If there is any error in entering any values to the database, the system generates the error message and asks the user to retry. This hel ps the user to be ensured that the values have been entered and hence a consistency in the system is maintained (Galitz 2009).Hardware InterfacesAs the system is a web based system, the website will be innkeepered on a central server machine with other machines getting access to it through the network. The other machines could be simple computers or especially dedicated machines that provide access only to the content. For our current implementation, we will rely on general desktop systems.Communications InterfacesThe system uses HTTP (hypertext transfer protocol) for sending and receiving data over the internet (Groth, Skandier, Lammle Tedder 2005). When the system is used within the hospital, it is presented on same network hence its generally faster as the server is also located within the hospital, but outside the hospital the system is accessible via internet and hence a domain is needed to be registered with the DNS servers hosted at the ISP.Data ModelThis section explains t he data baffle used for the system. The section begins with recognizing all the entities to be used in the system and their affinitys and then converting those entities and relations to control boards. These circumvents will be normalized to 3NF form. This section captures the cardinality and referential integrity rules needed to ensure that the data is of good quality for the users. The main aim of data models is to takeport the development of information systems by providing the definition and format of data.Entity-relationship modelThe E-R (entity-relationship) data model views the real world as a set of basic objects (entities) and relationships among these objects (Bai 2010). It is intended primarily for the DB design process by allowing the specification of an opening move scheme. If the information system, being designed, is based on a database then the conceptual data model will later be mapped on to a arranged data model, which in turn will be mapped on to a physical model during the physical design process (Bai 2010). The E-R diagram shows all objects involved in the system as entities and the function among them as relationships. Here is a description of entities used in our system-Entity An entity is nothing but an object that exists and is differentiable from other objects. Entities could be concrete such as a person or it could be an abstract entity that is nothing but a concept (Stallings 2008). An entity could also be considered as a source of information for the system. There are following entities in well meadows-Doctor or consultant (concrete)Change nurse (concrete)Patients (concrete)Wards (abstract)Drugs (concrete)Administrator (concrete)Staff (concrete)Qualification (abstract)Inpatient (concrete)Outpatient (concrete)Attributes Attributes are unique qualities that can be possessed by both relationships and entities. Attributes are represented by ovals that are connected to the entity sets that possess them by a line. With the exce ption of weak entities, all entities have to a minimum amount of attributes. These make up the primary distinguish of the entity (Stallings 2008). Following are the attributes of the various entities described above-Doctor id, name, address, telephone, duty open frame, date of sufferChange nurse id, name, address, telephone, date of birth, ward allocated.Patients id, name, address, telephone, date of birthWard ward_num, ward_name, location, in charge nurse, number of bedsDrugs id, name, type, dosage, methodology, price, stockAdministrator- username, password, name, address, telephone, date of birthStaff id, name, address, telephone, date of birth, ward allocated.Qualification- institution name, qualification nameInpatient- id, name, address, telephone, date of birth, date of admit, expected stay, expected date of leaving, actual date of leavingOutpatient id, name, address, telephone, date of birth, date of appointment, consultant name, location, time of appointment.Here i s an entity relationship diagram for the given system-(Entity Relationship Digram)The patients are categorized into inpatients and outpatients as explained above while the staff has two categories doctors and nurses. The remaining staff is covered chthonic staff itself. Wards are there in the hospital that is controlled by the nurses while drugs are referred by the doctors and they are taken by the patients. Both the inpatients and outpatients are treated by the doctors, while inpatients have a separate relationship with wards that they are admitted to it.Database design and normalizationNormalization can be defined as the process in which data is taken from problem and reduced to a set of relations through data integrity and elimination of data redundancy (Gunderloy Jorden 2008).Data integrity The data in the database is consistent and satisfies the all integrity constraints.Data redundancy Data redundancy incurs if it is found in two different locations (direct redundancy). At the same time the calculation of data from other items (indirect redundancy) also creates redundancy (Oppel 2004). prime(prenominal) normalized form The multi valued attributes are removed that facilitate a atomic number 53 value at the intersection of each row and column in a table.Second Normal form In second normal form, all the non key attributes must be dependent on complete primary key and not on a single part of primary key. triad normal form In a third normal form, all the non keys are determined only by the primary keys (Oppel 2004).Boyce-Codd normal form The anomalies have been removed that resulted from the functional dependancies (Gunderloy Jorden 2008).The normalized schemas of the tables used in our database are given below-Drugdrug_IDdrug_namedescriptiondosagemethodStockReordercostPatientpatient_idFirst NameLast nameAddresstelephoneDate of birthSexMarital statusDate of registrationStaffStaff_idFirst NameLast nameAddresstelephonepositionInpatientidPatient_idWard numberBed numberDate placedExpected periodExpected Date of leavingActual date of leavingWardWard numberNamelocationextensionCharge nurse id(staff.staff id)Outpatientidpatient idConsultant idDateTimelocationQualificationidStaff_idTypeInstitutionCompletion dateWeekly allocationWard numberStaff idshiftdatePrescriptionPatient_iddrug_idStart DateUnits per dayEnd dateDatabase implementationThe database defined above needs to be implemented over a database system. We use a relational database management system as our designs are based on relational model. Considering the requirements of hospital that are not very large, we can use an open source, free of cost database management system named as MySQL. MySQL is a relational database management system (RDBMS) that runs as a server providing multi-user access to a number of databases. It works on most of the available operating systems and is generally the most popular choice for implementing small database applications. It also has a plug-i n named as phpmyadmin that provides a GUI access to the database (Lambrix 2010). Here are the implementations of SQLs for the database- phpMyAdmin SQL Dump version 3.2.4 http//www.phpmyadmin.net Host localhost Generation Time Dec 12, 2010 at 0858 AM server version 5.1.41 PHP Version 5.3.1SET SQL_MODE=NO_AUTO_VALUE_ON_ZERO/*40101 SET emailprotectedCHARACTER_SET_CLIENT *//*40101 SET emailprotectedCHARACTER_SET_RESULTS *//*40101 SET emailprotectedCOLLATION_CONNECTION *//*40101 SET NAMES utf8 */ Database hospital Table structure for table drugCREATE slacken IF not EXISTS drug (drug_num int(11) not nobody AUTO_INCREMENT,name varchar(100) non shadowy,description varchar(100) not NULL,dosage varchar(100) not NULL,method varchar(100) NOT NULL,stock int(11) NOT NULL, rank int(11) inadvertence NULL,cost decimal(10,0) NOT NULL,PRIMARY KEY (drug_num)) ENGINE=MyISAM evasion CHARSET=latin1 AUTO_INCREMENT=1 Dumping data for table drug Table structure for table inpatientCREATE TABLE IF NOT E XISTS inpatient (inpatient_id int(11) NOT NULL AUTO_INCREMENT,patient_id int(11) NOT NULL,expected_stay int(11) NOT NULL,date_placed date NOT NULL,date_leave date DEFAULT NULL,actual_leave date DEFAULT NULL,ward_num int(11) NOT NULL,bed_num int(11) NOT NULL,spouse_id int(11) DEFAULT NULL,PRIMARY KEY (inpatient_id)) ENGINE=MyISAM DEFAULT CHARSET=latin1 AUTO_INCREMENT=2 Dumping data for table inpatientINSERT INTO inpatient (inpatient_id, patient_id, expected_stay, date_placed, date_leave, actual_leave, ward_num, bed_num, spouse_id) value(1, 1, 5, 2010-08-12, 0000-00-00, 0000-00-00, 1, 45, 0) Table structure for table outpatientCREATE TABLE IF NOT EXISTS outpatient (appointment_num int(11) NOT NULL AUTO_INCREMENT,consultant_id int(11) NOT NULL,patient_id int(11) NOT NULL,date date NOT NULL,time time NOT NULL,location varchar(100) NOT NULL,PRIMARY KEY (appointment_num)) ENGINE=MyISAM DEFAULT CHARSET=latin1 AUTO_INCREMENT=1 Dumping data for table outpatient Table structure for table pa tientCREATE TABLE IF NOT EXISTS patient (patient_id int(11) NOT NULL AUTO_INCREMENT,firstname varchar(50) NOT NULL,lastname varchar(50) NOT NULL,address varchar(500) NOT NULL,tel varchar(20) NOT NULL,dob date NOT NULL, commove varchar(10) NOT NULL,mar_status varchar(20) NOT NULL,reg_date timestamp NOT NULL DEFAULT CURRENT_TIMESTAMP,PRIMARY KEY (patient_id)) ENGINE=MyISAM DEFAULT CHARSET=latin1 AUTO_INCREMENT=3 Dumping data for table patientINSERT INTO patient (patient_id, firstname, lastname, address, tel, dob, sex, mar_status, reg_date) VALUES(1, yash, yash, yash, 7799, 0000-00-00, Male, UnMarried, 2010-12-08 000310) Table structure for table prescription drugCREATE TABLE IF NOT EXISTS prescription (prescription_id int(11) NOT NULL AUTO_INCREMENT,patent_id int(11) NOT NULL,drug_num int(11) NOT NULL,units per day int(11) NOT NULL,startdate date NOT NULL,enddate date NOT NULL,PRIMARY KEY (prescription_id)) ENGINE=MyISAM DEFAULT CHARSET=latin1 AUTO_INCREMENT=1 Dumping data for table prescription Table structure for table qualificationCREATE TABLE IF NOT EXISTS qualification (q_id int(11) NOT NULL AUTO_INCREMENT,staff_id int(11) NOT NULL,type varchar(100) NOT NULL,institution varchar(100) NOT NULL,date date NOT NULL,PRIMARY KEY (q_id)) ENGINE=MyISAM DEFAULT CHARSET=latin1 AUTO_INCREMENT=1 Dumping data for table qualification Table structure for table requetsCREATE TABLE IF NOT EXISTS requets (request_id int(11) NOT NULL AUTO_INCREMENT,ward_num int(11) NOT NULL,drug_num int(11) NOT NULL,quantity int(11) NOT NULL,date date NOT NULL,processed int(11) NOT NULL DEFAULT 0,process_date date DEFAULT NULL,PRIMARY KEY (request_id)) ENGINE=MyISAM DEFAULT CHARSET=latin1 AUTO_INCREMENT=1 Dumping data for table requets Table structure for table staffCREATE TABLE IF NOT EXISTS staff (staff_id int(11) NOT NULL AUTO_INCREMENT,firstname varchar(50) NOT NULL,lastname varchar(50) NOT NULL,address varchar(500) NOT NULL,sex varchar(10) NOT NULL,dob date NOT NULL,tel varchar(20) NO T NULL,position varchar(50) NOT NULL,PRIMARY KEY (staff_id)) ENGINE=MyISAM DEFAULT CHARSET=latin1 AUTO_INCREMENT=4 Dumping data for table staffINSERT INTO staff (staff_id, firstname, lastname, address, sex, dob, tel, position) VALUES(1, abcd, pqrs, asasd, Male, 0000-00-00, 123123, Charge Nurse) Table structure for table staffhierCREATE TABLE IF NOT EXISTS staffhier (id int(11) NOT NULL,description varchar(100) NOT NULL) ENGINE=MyISAM DEFAULT CHARSET=latin1 Dumping data for table staffhierINSERT INTO staffhier (id, description) VALUES(1, consultant),(2, Charge Nurse),(3, physiotherapist),(4, nurse) Table structure for table tblusersCREATE TABLE IF NOT EXISTS tblusers (username varchar(50) NOT NULL,password varchar(50) NOT NULL,name varchar(50) NOT NULL,wrong_count int(11) NOT NULL DEFAULT 0,PRIMARY KEY (username)) ENGINE=MyISAM DEFAULT CHARSET=latin1 Dumping data for table tblusersINSERT INTO tblusers (username, password, name, wrong_count) VALUES(admin, 123456, administrator, 1) Ta ble structure for table wardCREATE TABLE IF NOT EXISTS ward (ward_num int(11) NOT NULL AUTO_INCREMENT,ward_name varchar(50) NOT NULL,location varchar(100) NOT NULL,ext int(11) NOT NULL,num_beds int(11) NOT NULL,nurse_id int(11) NOT NULL,PRIMARY KEY (ward_num)) ENGINE=MyISAM DEFAULT CHARSET=latin1 AUTO_INCREMENT=2 Dumping data for table wardINSERT INTO ward (ward_num, ward_name, location, ext, num_beds, nurse_id) VALUES(1, ank, asasd, 6666, 3, 1) Table structure for table weeklyallocationCREATE TABLE IF NOT EXISTS weeklyallocation (allocation_id int(11) NOT NULL AUTO_INCREMENT,staff_id int(11) NOT NULL,ward_num int(11) NOT NULL,shift varchar(50) NOT NULL,startdate timestamp NOT NULL DEFAULT CURRENT_TIMESTAMP,PRIMARY KEY (allocation_id)) ENGINE=MyISAM DEFAULT CHARSET=latin1 AUTO_INCREMENT=4 Dumping data for table weeklyallocationINSERT INTO weeklyallocation (allocation_id, staff_id, ward_num, shift, startdate) VALUES(1, 1, 1, EARLY, 2010-12-07 185240),(2, 1, 1, NIGHT, 2010-12-07 233 340),(3, 0, 1, , 2010-12-08 000525)/*40101 SET emailprotected_CHARACTER_SET_CLIENT *//*40101 SET emailprotected_CHARACTER_SET_RESULTS *//*40101 SET emailprotected_COLLATION_CONNECTION */This script will create the database and will make few entries in the tables as well. The username and passwords are stored in a table named as tblUsers. The admin password is also stored in the same table. This is the dump of the database exported by using phpmyadmin. Same script can be executed using the tool or also can be imported using the import option in phpmyadmin (Lambrix 2010). This will setup the database and the application can now be configured.System implementationThe package package we choose for this system is XAMPP. Xampp is a software package that is used for hosting websites and the combination of four software packages namely php, apache, mysql and phpmyadmin. Xampp is a simple program that can be run on any machine it does not require any specific hardware. Xampp is free softwar e and it is available for various operating systems such as Linux, Windows, Mac OS, and Solaris etc. The programs sets up a mysql server on the system as well as an apache web server on the machine. The package also configures php for the machine and also provides phpmyadmin for managing the mysql database (Newman Thomas 2008). Xampp provides a root directory named as htdocs that works for the web server. Xampp is the easiest way to host a website. Xampp is very easy to install and uninstall as compared to the separate installation and configuration of the services it provides. Xampp also includes support for filezilla, mercury etc.DevelopersXampp is open source software developed by www.apachefriends.com. Apache friends were founded in 2002 by Oswald and Kay. Oswald is their webmaster, while Kay is the maintainer of apache for windows. Apache friends have Xampp as their only project (Newman Thomas 2008). There are no new projects till date. The software package is available throu gh Sourceforge that hosted the download files on their website www.sourceforge.net and made this whole project possible.BenefitsXampp has several benefits that make web hosting easy. These are as below It is available in many languages such as English, Dutch, Italian, French, Portuguese and Chinese etc.It makes database management very easy with support of phpmydmin.The sup