Hospitals currently use a manual system for visiting Doctor Slip as a token. The current system requires numerous paper forms, with data stores spread throughout the hospital management infrastructure. Often information (on forms) is incomplete, or does not follow management standards. Forms are often lost in transit between departments requiring a comprehensive auditing process to ensure that no vital information is lost. Multiple copies of the same information exist in the hospital and may lead to inconsistencies in data in various data stores. A significant part of the operation of any hospital involves the acquisition, management and timely retrieval of great volumes of information. This information typically involves; Doctor, Room, Department and Patient personal Information. All of this information must be managed in an efficient and cost wise fashion so that an institution's resources may be effectively utilized Hospital E-Token management will automate the management of the hospital making it more efficient and error free for outdoor patient. It aims at standardizing data, consolidating data ensuring data integrity and reducing inconsistencies.

1. 1
Hospital E-Token Management
(For Outdoor Patient)
Submitted To:
Syed Zahidul Hassan
Consultant (C# .Net Framework)
IDB-BISEW IT Scholarship Project.
Show & Tell Consulting Ltd. Submitted By:
1. Anisur Rahman
ID No: 1181340.
2. Abdur Rahim.
ID No: 1186405
3. Ruhul Amin.
ID No: 1185160
Round-25,
TSP: CCSL,
Batch: ID-ESAD-CS/CCSL-01M/R25/0. Submitted Date: 02.05.2016

2. 2
Contents:
Page No
1. Abstract ------------------------------------------------------------------------------------------------ 3
2. Project Overview ------------------------------------------------------------------------------------- 3
3. Software Requirements ------------------------------------------------------------------------------ 3-4
4. User Characteristics ---------------------------------------------------------------------------------- 4
5. Constrains ---------------------------------------------------------------------------------------------- 4
6. Feasibility Study --------------------------------------------------------------------------------------- 5-8
 Steps in feasibility analysis
 Technical feasibility
 Front-end and back-end selection
 Front-end selection
 Back-end Selection
 Economical feasibility
 Operational Feasibility
 Schedule feasibility
7. Data flow Diagrams (DFD) ------------------------------------------------------------------------------ 8-9
 Level 1 DFD:
 Level 2 DFD Registration form
 LEVEL 3 DFD LOGIN PROCESSES
8. Database Table ----------------------------------------------------------------------------------------- 10-11
 Doctor Table
 Department Table
 Room Table
 Doctor Category Table
 Patient Table
9. Database Diagram ------------------------------------------------------------------------------------- 11
10. Output Screens --------------------------------------------------------------------------------------- 12-17
11. Conclusion -------------------------------------------------------------------------------------------- 17

3. 3
Abstract
Objective :
Hospitals currently use a manual system for visiting Doctor Slip as a token. The current system
requires numerous paper forms, with data stores spread throughout the hospital management infrastructure.
Often information (on forms) is incomplete, or does not follow management standards. Forms are often lost
in transit between departments requiring a comprehensive auditing process to ensure that no vital
information is lost. Multiple copies of the same information exist in the hospital and may lead to
inconsistencies in data in various data stores.
A significant part of the operation of any hospital involves the acquisition, management and timely
retrieval of great volumes of information. This information typically involves; Doctor, Room, Department
and Patient personal Information. All of this information must be managed in an efficient and cost wise
fashion so that an institution's resources may be effectively utilized Hospital E-Token management will
automate the management of the hospital making it more efficient and error free for outdoor patient. It aims
at standardizing data, consolidating data ensuring data integrity and reducing inconsistencies.
PROJECT OVERVIEW :
 Project is related to Hospital E-Token Management.
 Main facilities available in this project are:-
 Maintaining records of outdoor patients.
 Providing billing details for outdoor patients.
 User or Administrator can search a Doctor/Doctor Category/Room/Department
and patient’s record by his/her name
SOFTWARE REQUIREMENTS :
Platform: Windows
Technologies Used (Back End):
 MVC 5,
 Entity Framework 6.0,
 Web API 2.2,

4. 4
 OData v4,
 Cors.
Technologies Used (Front End)
 HTML5,
 CSS3,
 Bootstrap,
 jQuery,
 AngularJS.
Database: SQL Server 2012
Deployment Environment: IIS 7 or higher, Windows Azure Web Hosting
Description:
 Authentication/Log In,
 Doctor Entry and Search Doctor By Name/Department Name,
 Department Entry,
 Doctor Category Entry.
 Room Entry,
 Patient Entry and view Details,
 Print Patient details as a Doctor Visiting Token.
User Characteristics:
Every user should be:
• Comfortable of working with computer.
• He must have knowledge in medical field.
• He must also have basic knowledge of English too.
Constraints:
• GUI is only in English.
• Login and password is used for identification of user and there is no facility for guest.

5. 5
Feasibility Study:
Depending on the results of the initial investigation the survey is now expanded to a more detailed
feasibility study. “FEASIBILITY STUDY” is a test of system proposal according to its workability, impact
of the organization, ability to meet needs and effective use of the resources. It focuses on these major
questions:
1. What are the user’s demonstrable needs and how does a candidate system
Meet them?
2. What resources are available for given candidate system?
3. What are the likely impacts of the candidate system on the organization?
4. Whether it is worth to solve the problem?
During feasibility analysis for this project, following primary areas of interest are to be
Considered. Investigation and generating ideas about a new system does this.
Steps in feasibility analysis:
Eight steps involved in the feasibility analysis are:
Form a project team and appoint a project leader.
Prepare system flowcharts.
Enumerate potential proposed system.
Define and identify characteristics of proposed system.
Determine and evaluate performance and cost effective of each proposed system.
Weight system performance and cost data.
Select the best-proposed system.
Prepare and report final project directive to management.

6. 6
Technical feasibility:
A study of resource availability that may affect the ability to achieve an acceptable system. This
evaluation determines whether the technology needed for the proposed system is available or not.
Can the work for the project be done with current equipment existing software technology &
available personal?
Can the system be upgraded if developed?
If new technology is needed then what can be developed?
This is concerned with specifying equipment and software that will successfully satisfy the user
requirement. The technical needs of the system may include:
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:
It must have a graphical user interface that assists employees that are not from IT
background.
Scalability and extensibility.
Flexibility.
Robustness.
According to the organization requirement and the culture.
Must provide excellent reporting features with good printing support.
Platform independent.
Easy to debug and maintain.
Event driven programming facility.
Front end must support some popular back end like MS SQL Server.
According to the above stated features we selected VB6.0 as the front-end for developing our project.

7. 7
Back-end Selection:
 Multiple user support.
 Efficient data handling.
 Provide inherent features for security.
 Efficient data retrieval and maintenance.
 Popularity.
 Operating System compatible.
 Easy to install.
 Various drivers must be available.
 Easy to implant with the Front-end.
According to above stated features we selected MS SQL Server as the backend.
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.
Economical feasibility:
Economic justification is generally the “Bottom Line” consideration for most systems. Economic
justification includes a broad range of concerns that includes cost benefit analysis. In this we weight the
cost and the benefits associated with the candidate system and if it suits the basic purpose of the
organization i.e. profit making, the project is making to the analysis and design phase.
The financial and the economic questions during the preliminary investigation are verified to estimate the
following:
 The cost to conduct a full system investigation.
 The cost of hardware and software for the class of application being considered.
 The benefits in the form of reduced cost.
 The proposed system will give the minute information, as a result the performance is
improved which in turn may be expected to provide increased profits.
 This feasibility checks whether the system can be developed with the available funds.
The Hospital E-Token Management does not require enormous amount of money
to be developed. This can be done economically if planned judicially, so it is
economically feasible. The cost of project depends upon the number of man hours
required.

8. 8
Operational Feasibility:
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.
Schedule feasibility:
Time evaluation is the most important consideration in the development of project. The time schedule
required for the developed of this project is very important since more development time effect machine
time, cost and cause delay in the development of other systems.
A reliable Hospital E-Token Management can be developed in the considerable amount of time.
Data Flow Diagrams (DFD):
A DFD i.e. Data Flow Diagram is a graphical tool, which has the purpose of clarifying system requirements
and identifying major transformation that will be programs in the system design. It depicts the information
flow and transformation that occurs, as data moves from input to output. The DFD provides a mechanism
for functional modeling as well as information flow modeling.
An external entity which can be a source or a destiny is represented by a solid square. It lies outside the
context of the system. A process indicates the work that is performed on data. A circle represents a process.
Data flow takes place between various components of the system & hence represented by an arrow mark.
A data store is a repository for data. It is represented by an open-ended rectangle.

9. 9
Level 1 DFD:
Figure-1: Data flow Diagrams
Level 2 DFD Registration form:
Figure-2: Login Process
LEVEL 3 DFD LOGIN PROCESSES:
Figure-3: Login Process
Hospital E-Token
Management
Administrator
Create and
Update
Information
Information
New User
User Email
New
Password
Confirmation
Password
Get User
Details
Reg.Confirmation
and go to Login
Form
Open
Login form
Enter User
Email and
Password
Check
User
Redirect
to Home
page
Verification

10. 10
Database Table:
1. Doctor Table:
2. Department Table:
3. Room Table:

11. 11
5. Doctor Category Table:
4. Patient Table:
Database Diagram:

12. 12
OUTPUT SCREENS:
1. Admin Registration Form:
2. Login Form:
3. Home Page:

13. 13
4. Doctor Entry Form:
5. Department Entry Form:

14. 14
6. Room Entry From:
7. Doctor Category Entry Form:

15. 15
8. Patient Entry Form:

16. 16
9. Doctor Visiting slip/E-Token of Patient:
10. About and Contact :

17. 17
Conclusion:
The project Hospital E-Token Management is for computerizing the working in a hospital. The software
takes care of all the requirements of an average hospital and iscapable to provide easy and effective
storage of information related to patients that come up to the hospital and Hospital Authority provide a
slip as a token for visiting desired doctor such as professore,Lecturer.The system also provides the facility
of backup as per the requirement.
The End