0% found this document useful (0 votes)
14 views69 pages

Saba Framework in Hospital Management

The document outlines a project for a Hospital Management System developed using Visual C# to improve the efficiency of hospital operations by computerizing patient and doctor information management. It discusses the limitations of the existing manual system and proposes a new system that enhances speed, accuracy, and data security. Additionally, it details the software and hardware requirements, tools used, and the advantages of the .NET Framework in developing the application.
Copyright
© All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
0% found this document useful (0 votes)
14 views69 pages

Saba Framework in Hospital Management

The document outlines a project for a Hospital Management System developed using Visual C# to improve the efficiency of hospital operations by computerizing patient and doctor information management. It discusses the limitations of the existing manual system and proposes a new system that enhances speed, accuracy, and data security. Additionally, it details the software and hardware requirements, tools used, and the advantages of the .NET Framework in developing the application.
Copyright
© All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd

Hospital Management System BIST,MCA

1. INTRODUCTION
This project work titled ”Hospital management system” is an attempt to provide some
systematic understanding about the function of Hospital .This project Visual C#
language. This project topic used Hospital management system and used to simulate
real word situations.
The project contains a comprehensive study of the function of the Hospital management
system.

1.1 About Existing System


System analysis is a detailed study of the various operations performed by a system and
their relationships within and outside of the system. Here the key question is – What all
problems exist in the present system? What must be done to solve the problem?
Analysis begins when a user or manager begins a study of the program using existing
system. During analysis, data collected on the various files, decision points and
transactions handled by the present system. The commonly used tools in the system are
Data Flow Diagram, interviews, etc. training, experience and common sense are

required for collection of relevant information needed to develop the system.

1.2 Problems in Existing System


The purpose of the project entitled as “HOSPITAL MANAGEMENT SYSTEM” is to
computerize the Front Office Management of Hospital to develop software which is
user friendly, simple, fast, and cost – effective. It deals with the collection of patient’s
information, diagnosis details, etc. Traditionally, it was done manually. The main
function of the system is to register and store patient details and doctor details and
retrieve these details as and when required, and also to manipulate these details
meaningfully System input contains patient details, diagnosis details; while system
output is to get these details on to the CRT screen.

1.3 Proposed System

Saba Idrees [0112CA143D30] 1


Hospital Management System BIST,MCA

The proposed system is very easy to operate. Speed and accuracy are the main
advantages of proposed system. There is no redundancy of data. The data are stored in
the computer’s secondary memories like hard disk, etc. it can be easily receive and used
at any time. The proposed system will easily handle all the data and the work done by
the existing systems. The proposed systems eliminate the drawbacks of the existing
system to a great extent and it provides tight security to data.

2. ORGANIZATION PROFILE

Saba Idrees [0112CA143D30] 2


Hospital Management System BIST,MCA

Advance Web Technologies is a business IT Company focused on the delivery of the


innovative web solutions to the public and commercial sectors. As the client base has
expanded through diligent service and corporate acquisitions, so too has desire to
provide innovative, custom solutions to each of clients.
 Our strategy is to work with leading product vendors to deliver solutions to
customers that meet their strategic business goal working in close partnership
with our customers, we apply our business skills to deploy these solutions in the
most effective manner. In addition, our core technical strengths are available to
customers who seek to customize and integrate with existing investments and
legacy systems.

 As our client-base and scope of services has expanded, so too has our desire to
provide innovative, custom solutions to each of our clients. With a seasoned
staff of talented professionals, A.W.T is able to offer a full spectrum of creative
services, technical and marketing services that go well beyond the basics of web
site development.

3. SYSTEM REQUIREMENT PROFILE

Saba Idrees [0112CA143D30] 3


Hospital Management System BIST,MCA

3.1 Software Requirements

Operating System Server: Windows XP

Database Server: Microsoft SQL Server-2005

Client: Microsoft Internet Explorer

Tools: Microsoft Visual Studio .Net-2008 (Framework 3.5)

User Interface: [Link] with Ajax

Code Behind: C#.Net

3.2 Hardware Requirements


Processor: Intel Pentium or More
RAM: 512 MB Ram
Hard Disk: PC with 20GB

4. TOOLS AND TECHNIQUES USED

Saba Idrees [0112CA143D30] 4


Hospital Management System BIST,MCA

4.1 INTRODUCTION TO .NET FRAMEWORK


The Microsoft .NET Framework is a software technology that is available with several
Microsoft Windows operating systems. It includes a large library of pre-coded solutions
to common programming problems and a virtual machine that manages the execution of
programs written specifically for the framework. The .NET Framework is a key
Microsoft offering and is intended to be used by most new applications created for the
Windows platform.
Programs written for the .NET Framework execute in a software environment that
manages the program's runtime requirements. Also part of the .NET Framework, this
runtime environment is known as the Common Language Runtime (CLR). The CLR
provides the appearance of an application virtual machine so that programmers need not
consider the capabilities of the specific CPU that will execute the program. The CLR
also provides other important services such as security, memory management, and
exception handling. The class library and the CLR together compose the .NET
Framework.

Principal design features

Interoperability
Because interaction between new and older applications is commonly required,
the .NET Framework provides means to access functionality that is implemented in
programs that execute outside the .NET environment. Access to COM components is
provided in the [Link] and [Link]
namespaces of the framework; access to other functionality is provided using the
P/Invoke feature.

Common Runtime Engine

Saba Idrees [0112CA143D30] 5


Hospital Management System BIST,MCA

The Common Language Runtime (CLR) is the virtual machine component of the .NET
framework. All .NET programs execute under the supervision of the CLR, guaranteeing
certain properties and behaviors in the areas of memory management, security, and
exception handling.

Base Class Library


The Base Class Library (BCL), part of the Framework Class Library (FCL), is a library
of functionality available to all languages using the .NET Framework. The BCL
provides classes which encapsulate a number of common functions, including file
reading and writing, graphic rendering, database interaction and XML document
manipulation.

Simplified Deployment
Installation of computer software must be carefully managed to ensure that it does not
interfere with previously installed software, and that it conforms to security
requirements. The .NET framework includes design features and tools that help address
these requirements.

Security
The design is meant to address some of the vulnerabilities, such as buffer overflows,
that have been exploited by malicious software. Additionally, .NET provides a common
security model for all applications.

Portability
The design of the .NET Framework allows it to theoretically be platform agnostic, and
thus cross-platform compatible. That is, a program written to use the framework should
run without change on any type of system for which the framework is implemented.
Microsoft's commercial implementations of the framework cover Windows, Windows
CE, and the Xbox 360. In addition, Microsoft submits the specifications for the

Saba Idrees [0112CA143D30] 6


Hospital Management System BIST,MCA

Common Language Infrastructure (which includes the core class libraries, Common
Type System, and the Common Intermediate Language), the C# language, and the C+
+/CLI language to both ECMA and the ISO, making them available as open standards.
This makes it possible for third parties to create compatible implementations of the
framework and its languages on other platforms.

Architecture

Visual overview of the Common Language Infrastructure (CLI)


Common Language Infrastructure

The core aspects of the .NET framework lie within the Common Language
Infrastructure, or CLI. The purpose of the CLI is to provide a language-neutral platform
for application development and execution, including functions for exception handling,
garbage collection, security, and interoperability. Microsoft's implementation of the CLI
is called the Common Language Runtime or CLR.

Assemblies

Saba Idrees [0112CA143D30] 7


Hospital Management System BIST,MCA

The intermediate CIL code is housed in .NET assemblies. As mandated by


specification, assemblies are stored in the Portable Executable (PE) format, common on
the Windows platform for all DLL and EXE files. The assembly consists of one or more
files, one of which must contain the manifest, which has the metadata for the assembly.

Metadata
All CLI is self-describing through .NET metadata. The CLR checks the metadata to
ensure that the correct method is called. Metadata is usually generated by language
compilers but developers can create their own metadata through custom attributes.
Metadata contains information about the assembly, and is also used to implement the
reflective programming capabilities of .NET Framework.

Security
.NET has its own security mechanism with two general features: Code Access Security
(CAS), and validation and verification. Code Access Security is based on evidence that
is associated with a specific assembly. Typically the evidence is the source of the
assembly (whether it is installed on the local machine or has been downloaded from the
intranet or Internet). Code Access Security uses evidence to determine the permissions
granted to the code. Other code can demand that calling code is granted a specified
permission. The demand causes the CLR to perform a call stack walk: every assembly
of each method in the call stack is checked for the required permission; if any assembly
is not granted the permission a security exception is thrown.

Microsoft .NET Framework includes a set of standard class libraries. The class library
is organized in a hierarchy of namespaces. Most of the built in APIs are part of either
System.* or Microsoft.* namespaces. It encapsulates a large number of common
functions, such as file reading and writing, graphic rendering, database interaction, and
XML document manipulation, among others. The .NET class libraries are available to
all .NET languages. The .NET Framework class library is divided into two parts: the
Base Class Library and the Framework Class Library.

Saba Idrees [0112CA143D30] 8


Hospital Management System BIST,MCA

Memory management
The .NET Framework CLR frees the developer from the burden of managing memory
(allocating and freeing up when done); instead it does the memory management itself.
To this end, the memory allocated to instantiations of .NET types (objects) is done
contiguously from the managed heap, a pool of memory managed by the CLR. As long
as there exists a reference to an object, which might be either a direct reference to an
object or via a graph of objects, the object is considered to be in use by the CLR.

Versions: Microsoft started development on the .NET Framework in the late 1990s
originally under the name of Next Generation Windows Services (NGWS). By late
2000 the first beta versions of .NET 1.0 were released.

Version Version Number Release Date


1.0 1.0.3705.0 2002-01-05
1.1 1.1.4322.573 2003-04-01

Saba Idrees [0112CA143D30] 9


Hospital Management System BIST,MCA

2.0 2.0.50727.42 2005-11-07


3.0 3.0.4506.30 2006-11-06
3.5 3.5.21022.8 2007-11-09

4.2 [Link]

SERVER APPLICATION DEVELOPMENT


Server-side applications in the managed world are implemented through runtime hosts.
Unmanaged applications host the common language runtime, which allows your custom
managed code to control the behavior of the server. This model provides you with all
the features of the common language runtime and class library while gaining the
performance and scalability of the host server.

SERVER-SIDE MANAGED CODE


[Link] is the hosting environment that enables developers to use the .NET
Framework to target Web-based applications. However, [Link] is more than just a
runtime host; it is a complete architecture for developing Web sites and Internet-
distributed objects using managed code. Both Web Forms and XML Web services use
IIS and [Link] as the publishing mechanism for applications, and both have a
collection of supporting classes in the .NET Framework.
The .NET Framework also provides a collection of classes and tools to aid in
development and consumption of XML Web services applications. XML Web services
are built on standards such as SOAP (a remote procedure-call protocol), XML (an
extensible data format), and WSDL ( the Web Services Description Language).
The .NET Framework is built on these standards to promote interoperability with non-
Microsoft solutions.

ACTIVE SERVER [Link]

Saba Idrees [0112CA143D30] 10


Hospital Management System BIST,MCA

[Link] is a programming framework built on the common language runtime that can
be used on a server to build powerful Web applications. [Link] offers several
important advantages over previous Web development models:

 Enhanced Performance. [Link] is compiled common language runtime code


running on the server. Unlike its interpreted predecessors, [Link] can take
advantage of early binding, just-in-time compilation, native optimization, and
caching services right out of the box. This amounts to dramatically better
performance before you ever write a line of code.

 World-Class Tool Support. The [Link] framework is complemented by a rich


toolbox and designer in the Visual Studio integrated development environment.
WYSIWYG editing, drag-and-drop server controls, and automatic deployment are
just a few of the features this powerful tool provides.

 Power and Flexibility. Because [Link] is based on the common language


runtime, the power and flexibility of that entire platform is available to Web
application developers. The .NET Framework class library, Messaging, and Data
Access solutions are all seamlessly accessible from the Web. [Link] is also
language-independent, so you can choose the language that best applies to your
application or partition your application across many languages. Further, common
language runtime interoperability guarantees that your existing investment in COM-
based development is preserved when migrating to [Link].

 Simplicity. [Link] makes it easy to perform common tasks, from simple form
submission and client authentication to deployment and site configuration. For
example, the [Link] page framework allows you to build user interfaces that
cleanly separate application logic from presentation code and to handle events in a
simple, Visual Basic - like forms processing model. Additionally, the common

Saba Idrees [0112CA143D30] 11


Hospital Management System BIST,MCA

language runtime simplifies development, with managed code services such as


automatic reference counting and garbage collection.

 Manageability. [Link] employs a text-based, hierarchical configuration system,


which simplifies applying settings to your server environment and Web
applications. Because configuration information is stored as plain text, new settings
may be applied without the aid of local administration tools. This "zero local
administration" philosophy extends to deploying [Link] Framework applications
as well. An [Link] Framework application is deployed to a server simply by
copying the necessary files to the server. No server restart is required, even to
deploy or replace running compiled code.

 Scalability and Availability. [Link] has been designed with scalability in mind,
with features specifically tailored to improve performance in clustered and
multiprocessor environments. Further, processes are closely monitored and managed
by the [Link] runtime, so that if one misbehaves (leaks, deadlocks), a new
process can be created in its place, which helps keep your application constantly
available to handle requests.
 Customizability and Extensibility. [Link] delivers a well-factored architecture
that allows developers to "plug-in" their code at the appropriate level. In fact, it is
possible to extend or replace any subcomponent of the [Link] runtime with your
own custom-written component. Implementing custom authentication or state
services has never been easier.

 Security. With built in Windows authentication and per-application configuration,


you can be assured that your applications are secure.

Saba Idrees [0112CA143D30] 12


Hospital Management System BIST,MCA

LANGUAGE SUPPORT
The Microsoft .NET Platform currently offers built-in support for three languages: C#,
Visual Basic, and Java Script.

WHAT IS [Link] WEB FORMS?


The [Link] Web Forms page framework is a scalable common language runtime
programming model that can be used on the server to dynamically generate Web pages.

Intended as a logical evolution of ASP ([Link] provides syntax compatibility with


existing pages), the [Link] Web Forms framework has been specifically designed to
address a number of key deficiencies in the previous model. In particular, it provides:
 The ability to create and use reusable UI controls that can encapsulate common
functionality and thus reduce the amount of code that a page developer has to write.
 The ability for developers to cleanly structure their page logic in an orderly fashion
(not "spaghetti code").
 The ability for development tools to provide strong WYSIWYG design support for
pages (existing ASP code is opaque to tools).

[Link] Web Forms pages are text files with an .aspx file name extension. They can
be deployed throughout an IIS virtual root directory tree. When a browser client
requests .aspx resources, the [Link] runtime parses and compiles the target file into a
.NET Framework class. This class can then be used to dynamically process incoming
requests. (Note that the .aspx file is compiled only the first time it is accessed; the
compiled type instance is then reused across multiple requests).

An [Link] page can be created simply by taking an existing HTML file and
changing its file name extension to .aspx (no modification of code is required). For
example, the following sample demonstrates a simple HTML page that collects a user's

Saba Idrees [0112CA143D30] 13


Hospital Management System BIST,MCA

name and category preference and then performs a form post back to the originating
page when a button is clicked:

[Link] provides syntax compatibility with existing ASP pages. This includes support
for <% %> code render blocks that can be intermixed with HTML content within
an .aspx file. These code blocks execute in a top-down manner at page render time.

CODE-BEHIND WEB FORMS


[Link] supports two methods of authoring dynamic pages. The first is the method
shown in the preceding samples, where the page code is physically declared within the
originating .aspx file. An alternative approach--known as the code-behind method--
enables the page code to be more cleanly separated from the HTML content into an
entirely separate file.
INTRODUCTION TO [Link] SERVER CONTROLS
In addition to (or instead of) using <% %> code blocks to program dynamic content,
[Link] page developers can use [Link] server controls to program Web pages.
Server controls are declared within an .aspx file using custom tags or intrinsic HTML
tags that contain a runat="server" attributes value. Intrinsic HTML tags are handled by
one of the controls in the [Link] namespace. Any tag that
doesn't explicitly map to one of the controls is assigned the type of
[Link].

Server controls automatically maintain any client-entered values between round trips to
the server. This control state is not stored on the server (it is instead stored within an
<input type="hidden"> form field that is round-tripped between requests). Note also
that no client-side script is required.

In addition to supporting standard HTML input controls, [Link] enables developers


to utilize richer custom controls on their pages. For example, the following sample

Saba Idrees [0112CA143D30] 14


Hospital Management System BIST,MCA

demonstrates how the <asp:adrotator> control can be used to dynamically display


rotating ads on a page.

1. [Link] Web Forms provide an easy and powerful way to build dynamic Web UI.
2. [Link] Web Forms pages can target any browser client (there are no script
library or cookie requirements).
3. [Link] Web Forms pages provide syntax compatibility with existing ASP pages.
4. [Link] server controls provide an easy way to encapsulate common
functionality.
5. [Link] ships with 45 built-in server controls. Developers can also use controls
built by third parties.
6. [Link] server controls can automatically project both uplevel and downlevel
HTML.
7. [Link] templates provide an easy way to customize the look and feel of list
server controls.
8. [Link] validation controls provide an easy way to do declarative client or server
data validation.

4.3 C#.NET

[Link] OVERVIEW
[Link] is an evolution of the ADO data access model that directly addresses user
requirements for developing scalable applications. It was designed specifically for the
web with scalability, statelessness, and XML in mind.
[Link] uses some ADO objects, such as the Connection and Command objects, and
also introduces new objects. Key new [Link] objects include the Dataset, Data
Reader, and Data Adapter.
The following sections will introduce you to some objects that have evolved, and some
that are new. These objects are:

Saba Idrees [0112CA143D30] 15


Hospital Management System BIST,MCA

 Connections. For connection to and managing transactions against a database.


 Commands. For issuing SQL commands against a database.
 DataReaders. For reading a forward-only stream of data records from a SQL Server
data source.
 DataSet. For storing, Remoting and programming against flat data, XML data and
relational data.
 DataAdapters. For pushing data into a DataSet, and reconciling data against a
database.

Connections:
Connections are used to 'talk to' databases, and are represented by provider-specific
classes such as SqlConnection. Commands travel over connections and resultsets are
returned in the form of streams which can be read by a DataReader object, or pushed
into a DataSet object.

Commands:
Commands contain the information that is submitted to a database, and are represented
by provider-specific classes such as SqlCommand. A command can be a stored
procedure call, an UPDATE statement, or a statement that returns results. You can also
use input and output parameters, and return values as part of your command syntax. The
example below shows how to issue an INSERT statement against the Northwind
database.

DataReaders:
The DataReader object is somewhat synonymous with a read-only/forward-only cursor
over data. The DataReader API supports flat as well as hierarchical data. A DataReader
object is returned after executing a command against a database. The format of the
returned DataReader object is different from a recordset. For example, you might use
the DataReader to show the results of a search list in a web page.

Saba Idrees [0112CA143D30] 16


Hospital Management System BIST,MCA

DATA SETS AND DATA ADAPTERS:


DataSets
The DataSet object is similar to the ADO Recordset object, but more powerful, and with
one other important distinction: the DataSet is always disconnected. The DataSet object
represents a cache of data, with database-like structures such as tables, columns,
relationships, and constraints. However, though a DataSet can and does behave much
like a database, it is important to remember that DataSet objects do not interact directly
with databases, or other source data.

DATA ADAPTERS (OLEDB/SQL)


The DataAdapter object works as a bridge between the DataSet and the source data.
Using the provider-specific SqlDataAdapter (along with its associated SqlCommand
and SqlConnection) can increase overall performance when working with a Microsoft
SQL Server databases. For other OLE DB-supported databases, you would use the
OleDbDataAdapter object and its associated OleDbCommand and OleDbConnection
objects.
1. [Link] is the next evolution of ADO for the .Net Framework.
2. [Link] was created with n-Tier, statelessness and XML in the forefront. Two
new objects, the DataSet and DataAdapter, are provided for these scenarios.
3. [Link] can be used to get data from a stream, or to store data in a cache for
updates.
4. There is a lot more information about [Link] in the documentation.
Also, you can use a DataSet to bind to the data, move through the data, and
navigate data relationships.

4.4 SQL SERVER -2005


A database management, or DBMS, gives the user access to their data and helps them
transform the data into information. Such database management systems include dBase,

Saba Idrees [0112CA143D30] 17


Hospital Management System BIST,MCA

paradox, IMS, SQL Server and SQL Server. These systems allow users to create,
update and extract information from their database.
A database is a structured collection of data. Data refers to the characteristics of people,
things and events. SQL Server stores each data item in its own fields. In SQL Server,
the fields relating to a particular person, thing or event are bundled together to form a
single complete unit of data, called a record (it can also be referred to as raw or an
occurrence). Each record is made up of a number of fields. No two fields in a record
can have the same field name.
During an SQL Server Database design project, the analysis of your business needs
identifies all the fields or attributes of interest. If your business needs change over time,
you define any additional fields or change the definition of existing fields.

SQL SERVER TABLES


SQL Server stores records relating to each other in a table. Different tables are created
for the various groups of information. Related tables are grouped together to form a
database.

PRIMARY KEY
Every table in SQL Server has a field or a combination of fields that uniquely identifies
each record in the table. The Unique identifier is called the Primary Key, or simply the
Key. The primary key provides the means to distinguish one record from all other in a
table. It allows the user and the database system to identify, locate and refer to one
particular record in the database.

RELATIONAL DATABASE
Sometimes all the information of interest to a business operation can be stored in one
table. SQL Server makes it very easy to link the data in multiple tables. This is what

Saba Idrees [0112CA143D30] 18


Hospital Management System BIST,MCA

makes SQL Server a relational database management system, or RDBMS. It stores data
in two or more tables and enables you to define relationships between the table and
enables you to define relationships between the tables.

FOREIGN KEY:
When a field is one table matches the primary key of another field is referred to as a
foreign key. A foreign key is a field or a group of fields in one table whose values
match those of the primary key of another table.

PROJECT PLAN
The purpose of software project planning is to establish reasonable plans for performing
the software engineering and for managing the software project. “Software Project
Planning” involves developing estimates for the work to be performed, establishing the
necessary commitment, and defining the plan to perform the work. The software
planning begins with a statement of the work to be performed and other constraints and
goals that define and bound the software. The software planning process includes steps
to estimate the size of the software work products and the resources needed, produce a
schedule, identify and assess software risks, and negotiate commitments. Iterating
through these steps may be necessary to establish the plan for the software project. This
plan provides the basis for performing and managing the software project’s activities
and addresses the commitments to the software project’s employee according to the
resources, constraints, and capabilities of the software project.

The MWO System Project Plan will provide a definition of the project, including the
project’s goals and objectives. Additionally, the Plan will serve as an agreement
between the following parties: Project Sponsor, Steering Committee, Project Manager,
Project Team, and other personnel associated with and/or affected by the project. A plan
that demonstrates what is possible, shows an overall path and clear responsibilities, and
contains the details for estimating the people, money, time, equipment, and materials

Saba Idrees [0112CA143D30] 19


Hospital Management System BIST,MCA

necessary to get the job done, and will be used to measure progress during the project
and act as an early warning system.

Project Management is a vast subject covering project management planning, tools,


methodologies, processes and many more. It requires both practical and conceptual
study. Project Management- Systems Approach to Planning, Scheduling, and
Controlling Covers the basic principles of management like planning, allocation of
resources, scheduling, directing, monitoring, assessing, remedying any snags, and
finally closing up.

The Project Plan defines the following

 Project purpose.

 Business and project goals and objectives.

 Scope and expectations.

 Roles and responsibilities.

 Assumptions and constraints.

 Project management approach.

 Project budget.

 Project timeline.

 The conceptual design of new technology.

The Test Plan

The test plan is a mandatory document. You can’t test without one. For simple, straight-
forward projects the plan doesn’t have to be elaborate but it must address certain items.
As identified by the “American National Standards Institute and Institute for Electrical
and Electronic Engineers Standard 829/1983 for Software Test Documentation”, the
following components should be covered in a software test plan.

5.1 Software Project Estimation

Saba Idrees [0112CA143D30] 20


Hospital Management System BIST,MCA

Effective software project estimation is one of the most challenging and important
activities in software development. Proper project planning and control is not possible
without a sound and reliable estimate. As a whole, the software industry doesn’t
estimate projects well and doesn’t use estimates appropriately.

5.2 Scheduling

Software project scheduling is an activity that distributes estimated efforts across the
planned project duration by allocating the effort to specific software engineering tasks.
The basic principles adopted for software project scheduling are:

 Compartmentalization.
 Interdependency.
 Time Allocation.
 Effort validation

MODULES OF DISCRIPTION
To understand the activities of ward incharge more clearly, his activities are described
in details in the following section.

WARD MAINTANANCE
Ward incharge maintenance the information of all wards of the hospital. For this he
maintains a ward register. He assigns a unique each ward. He enters a fresh entry
regarding a ward as soon as a new is added in the hospital. Using this register in the
morning, ward incharge prepares a list of vacant wards. This list helps them in deciding
the course of action for rest of the day. If wards are free then only doctors
recommended patient to get admitted in the hospital.

PATIENT REGISTRATION
In this department all new patient are registered. Format of admission slip is described
below. Registration incharge enters the details of patient in the registration register.
After allotting the unique registration number to the patient, he also collect the
registration fee.

Saba Idrees [0112CA143D30] 21


Hospital Management System BIST,MCA

TREATMENT REGISTER
This register maintain by the doctors. After examine a patient the suggested
recommendations & medicines are entered by the doctors in this register according to
Reno of patient.

PATHOLOGY REGISTER
In this section the patient pathology checkups are done according to Doctor’s
recommendation. The pathology incharge maintain the pathology register on the basis
of patient’s registration register.

DOCTOR REGISTER
In this register the hospital maintain the record of doctors. The hospital allotted a unique
decode to each doctor.

BILL & FINAL REPORT GENERATION


When a patient is cured, doctor sends a discharge slip to ward incharge. After getting
discharge slip, Ward incharge discharge the patient and generate final bill & report of
patient .

MONEY COLLECTION
After generating the bill, ward incharge charges money from the patient and performs
the following functions:
A). Updates discharge register to the record the information of amount collected
date of discharge & final report.
B) Updates ward registers, so as to have the wards status as vacant.

6. SYSTEM ANALYSIS
FEASUBILITY STUDY

Saba Idrees [0112CA143D30] 22


Hospital Management System BIST,MCA

The main objective of the feasibility study is to test the Technical, Operational and
Economical feasibility for adding new modules and debugging old running system. All
system is feasible if they are unlimited resources and infinite time. Technical Feasibility

 Operational Feasibility
 Economical Feasibility

6.1 TECHNICAL FEASIBILITY

Technical Feasibility centers on the existing computer system hardware, software, etc.
and to some extent how it can support the proposed addition. This involves financial
considerations to accommodate technical enhancements. Technical support is also a
reason for the success of the project. Since the project is designed with [Link] with
C# as Front end and SQL Server 2000 as Back end, it is easy to install in all the systems
wherever needed. It is more efficient, easy and user-friendly to understand by almost
everyone.

6.2 OPERATIONAL FEASIBILITY

People are inherently instant to change and computers have been known to facilitate
change. An estimate should be made to how strong a reaction the user staff is likely to
have towards the development of the computerized system. The staff is accustomed to
computerized systems. These kinds of systems are becoming more common day by day
for evaluation of the software engineers. Hence, this system is operationally feasible. As
this system is technically, economically and operationally feasible, this system is judged
feasible.

6.3 ECONOMICAL FEASIBILIT

Saba Idrees [0112CA143D30] 23


Hospital Management System BIST,MCA

The role of interface design is to reconcile the differences that prevail among the
software engineer’s design model, the designed system meet the end user requirement
with economical way at minimal cost within the affordable price by encouraging more
of proposed system. Economic feasibility is concerned with comparing the development
cost with the income/benefit derived from the developed system.

7. DESIGN
Software design sits at the technical kernel of the software engineering process and is
applied regardless of the development paradigm and area of application. Design is the
first step in the development phase for any engineered product or system. The
designer’s goal is to produce a model or representation of an entity that will later be
built. Beginning, once system requirement have been specified and analyzed, system
design is the first of the three technical activities -design, code and test that is required
to build and verify software.

Saba Idrees [0112CA143D30] 24


Hospital Management System BIST,MCA

7.1 ER Diagram

7.2 DFD

Saba Idrees [0112CA143D30] 25


Hospital Management System BIST,MCA

0 Level DFD

1 Level DFD

2 Level DFD

Saba Idrees [0112CA143D30] 26


Hospital Management System BIST,MCA

Tables

Saba Idrees [0112CA143D30] 27


Hospital Management System BIST,MCA

Structure of Hospital Management tbl_addnew_ward:-

Field_Name Field_Type Size Keys


category Varchar 50 Primary key
Ward_no varchar 50
Ward_charges Int

Structure of Hospital Management tbl_admin_login:-

Field_Name Field_Type Size Keys


username Varchar 50 Primary key
password varchar 50

structure of Hospital Management tbl_discharge:-

Field_Name Field_Type Size Keys


Reg_no Varchar 50 Primary key
Doc_name varchar 50
Fees_for_medicine Float
Fees_for_patho float
Fees_for_xrey float
Fees_for_altrasound float
No._of_day_inaward float
Ward_perday_charge float
Total_ward_charge float
Total_fees float

Structure of Hospital Management tbl_doc_advice:-

Field_Name Field_Type Size Keys


Patient_reg_no Varchar 50 Primary key
Advice_report varchar 50

Structure of Hospital Management tbl_doc_info:-

Saba Idrees [0112CA143D30] 28


Hospital Management System BIST,MCA

Field_Name Field_Type Size Keys


id Varchar 50 Primary key
doj varchar 50
name varchar 50
address varchar 50
department varchar 50
ddday varchar 15
ddmonth varcahar 15
ddyear varcahar 15
qualification varchar 50

Structure of Hospital Management tbl_emp:-

Field_Name Field_Type Size Keys


name Varchar 50 Primary key
designation varchar 50
dob varchar 50
salary Int
doj varcahr 50

Structure of Hospital Management tbl_path_test:-

Field_Name Field_Type Size Keys


Doc_code Varchar 50
Doc_path_name varchar 50
Regi_no Int Primary key
Test_name1 varchar 50
Result1 varchar 50
Achual_date1 varchar 50
Text_name2 varchar 50
Result2 varchar 50
Achual_date2 varchar 50
Text_name3 varchar 50
Result3 varchar 50
Achual_date3 varchar 50
Text_name varchar 50

Structure of Hospital Management tbl_patient_reg:-

Saba Idrees [0112CA143D30] 29


Hospital Management System BIST,MCA

Field_Name Field_Type Size Keys


id Int Primary key
address varchar 50
sex varcahr 10
department varchar 50
docname varchar 50
age Int
fees Float
Regdate varchar 50

Structure of Hospital Management tbl_treatment:-

Field_Name Field_Type Size Keys


Id Int
Reg_no Int 50 Primary key
Doc_code varcahr 10
Disese_dig varchar 500
medicine varchar 500
Path_test varchar 500
Xray Bit
Ultra Bit
Operation_ifany varchar 50

Structure of Hospital Management tbl_ultrasound:-

Field_Name Field_Type Size Keys


registration Int Primary key
Doc_code varchar 50
Radiologist_name varcahr 10
Ultra_detail1 varchar 50
Report1 varchar 50
Ultra_detail2 varchar 50
Report2 varchar 50
Date_of_ultrasoun varchar 50
d

Structure of Hospital Management tbl_ward_screen:-

Saba Idrees [0112CA143D30] 30


Hospital Management System BIST,MCA

Field_Name Field_Type Size Keys


id Int Primary key
catogary varchar 50
wardno varcahr 10
Reg_no varchar 50
Fees_advance Int
date varchar 50

Structure of Hospital Management tbl_xray:-

Field_Name Field_Type Size Keys


registration Int Primary key
Doc_code Int
Radio_name varcahr 10
Xray_detail1 varchar 50
Report1 varchar 50
Xray_detail2 varchar 50
Report2 varchar 50
Date_of_xray varchar 50

8. WORKING LAYOUT OF FORMS

Saba Idrees [0112CA143D30] 31


Hospital Management System BIST,MCA

[Link]

About [Link]

Saba Idrees [0112CA143D30] 32


Hospital Management System BIST,MCA

Patient [Link]

Saba Idrees [0112CA143D30] 33


Hospital Management System BIST,MCA

Contact [Link]

Saba Idrees [0112CA143D30] 34


Hospital Management System BIST,MCA

Saba Idrees [0112CA143D30] 35


Hospital Management System BIST,MCA

Feature [Link]

Saba Idrees [0112CA143D30] 36


Hospital Management System BIST,MCA

Bariartric [Link]

Saba Idrees [0112CA143D30] 37


Hospital Management System BIST,MCA

Cosmetic [Link]

Saba Idrees [0112CA143D30] 38


Hospital Management System BIST,MCA

(Cosmetic surgery) Hair [Link]

Saba Idrees [0112CA143D30] 39


Hospital Management System BIST,MCA

(Cosmetic Surgery) Cosmetic surgery For Face\Nose\[Link]

Saba Idrees [0112CA143D30] 40


Hospital Management System BIST,MCA

Cosmetic Surgery) Nose [Link]

Saba Idrees [0112CA143D30] 41


Hospital Management System BIST,MCA

[Link]

Saba Idrees [0112CA143D30] 42


Hospital Management System BIST,MCA

(Replacement) Hip Replacement [Link]

(Replacement) Orthopedics And Joint [Link]

Saba Idrees [0112CA143D30] 43


Hospital Management System BIST,MCA

(Replacement) Spine [Link]

Saba Idrees [0112CA143D30] 44


Hospital Management System BIST,MCA

Cardiology And Cardio Thoracic [Link]

Saba Idrees [0112CA143D30] 45


Hospital Management System BIST,MCA

Hand And Micro [Link]

Saba Idrees [0112CA143D30] 46


Hospital Management System BIST,MCA

[Link]

Saba Idrees [0112CA143D30] 47


Hospital Management System BIST,MCA

(Transplants) Center For Liver Disease and [Link]

Saba Idrees [0112CA143D30] 48


Hospital Management System BIST,MCA

Nephrology And [Link]

Saba Idrees [0112CA143D30] 49


Hospital Management System BIST,MCA

Neurology And Neuro [Link]

Saba Idrees [0112CA143D30] 50


Hospital Management System BIST,MCA

[Link]

Saba Idrees [0112CA143D30] 51


Hospital Management System BIST,MCA

Saba Idrees [0112CA143D30] 52


Hospital Management System BIST,MCA

[Link]

Saba Idrees [0112CA143D30] 53


Hospital Management System BIST,MCA

[Link]

Saba Idrees [0112CA143D30] 54


Hospital Management System BIST,MCA

Patient [Link]

Saba Idrees [0112CA143D30] 55


Hospital Management System BIST,MCA

Doctar [Link]

Saba Idrees [0112CA143D30] 56


Hospital Management System BIST,MCA

Ward [Link]

Saba Idrees [0112CA143D30] 57


Hospital Management System BIST,MCA

Add New [Link]

Saba Idrees [0112CA143D30] 58


Hospital Management System BIST,MCA

[Link]

Saba Idrees [0112CA143D30] 59


Hospital Management System BIST,MCA

Discharge [Link]

Saba Idrees [0112CA143D30] 60


Hospital Management System BIST,MCA

Pathalogy [Link]

Saba Idrees [0112CA143D30] 61


Hospital Management System BIST,MCA

Xray [Link]

Saba Idrees [0112CA143D30] 62


Hospital Management System BIST,MCA

Ultrasound [Link]

Saba Idrees [0112CA143D30] 63


Hospital Management System BIST,MCA

Patient [Link]

Saba Idrees [0112CA143D30] 64


Hospital Management System BIST,MCA

Saba Idrees [0112CA143D30] 65


Hospital Management System BIST,MCA

10. TESTING
During testing the program to tested is executed with the set of test cases and have the
output of the program for the test cases is evaluated to determine if the program is
performing as expected. Due to its approach dynamic testing can only presence of errors
in the program, the exact nature of errors is not usually decided by testing. Testing
forms is the first in determining errors in the program. Once a program are tested
individually then the system as a whole needs to be tested. During testing the system is
used experimentally to ensure that the software does not fail i.e. it will run according to
its specification. The programs executed to check for any syntax and logical errors. The
errors are corrected and test is made to determine whether the program is doing what
supposed to do.

Software Testing is an empirical investigation conducted to provide stakeholders with


information about the quality of the product or service under test, with respect to the
context in which it is intended to operate. Software Testing also provides an objective,
independent view of the software to allow the business to appreciate and understand the
risks at implementation of the software. Test techniques include, but are not limited to,
the process of executing a program or application with the intent of finding software
bugs. It can also be stated as the process of validating and verifying that a software
program/application/product meets the business and technical requirements that guided
its design and development, so that it works as expected and can be implemented with
the same characteristics.

Software Testing, depending on the testing method employed, can be implemented at


any time in the development process, however the most test effort is employed after the
requirements have been defined and coding process has been completed. It is the
process to identify all defects existing in a software product. Testing can show the
presence of faults in a system; it cannot prove there are no remaining faults. Testing a
program consists of subjecting the program to a set of test inputs and observing if the
program behaves as expected, then the condition under which failure occurs are noted.

Saba Idrees [0112CA143D30] 66


Hospital Management System BIST,MCA

11. FUTURE ENHANCEMENT


This web site provides complete information about the Prayag Hospital. his time this
application automate the process of treatment in the manner that any process can check
their all type of support of a particular patient and admin of the web site hold the
records of doctors and employees of the Hospital .In future if any need facility will be
added in Hospital we will costly integrate it with site .

Saba Idrees [0112CA143D30] 67


Hospital Management System BIST,MCA

12. CONCLUSION
The Hospital Management System is very easy to operate. Speed and accuracy are the
main advantages of Hospital Management System. There is no redundancy of data. The
data are stored in the computer’s secondary memories like hard disk, etc. it can be
easily receive and used at any time. The Hospital Management System will easily
handle all the data and the work done by the existing systems.
The major achievement of this project is the ability register new staff, doctors, and
nurse and store their data in database the most important things that must be appreciated
by all is that, the system is an eye opener to a lot more investigation and detail research
for implementation and improvement purpose in order to add to the general knowledge
base.

Saba Idrees [0112CA143D30] 68


Hospital Management System BIST,MCA

13. REFERENCES
 Professional C# 2005

 Microsoft SQL Server 2005

 System Analysis and Design –Elias [Link]

 Black book

 Professional ASP .NET 3.5 -Wrox

Saba Idrees [0112CA143D30] 69

Common questions

Powered by AI

ASP.NET Framework enhances security during deployment through built-in Windows authentication and per-application configuration, ensuring application security. Additionally, the 'zero local administration' philosophy simplifies deployment, as applications are deployed merely by copying files to the server without needing server restarts, making it straightforward to secure updates or replacements .

Code Access Security (CAS) in Microsoft .NET Framework is a means of limiting the permissions granted to code based on evidence associated with specific assemblies, such as their source (local machine, intranet, or Internet). CAS uses this evidence to determine permissions, with the additional capability for code to demand that calling code possesses certain permissions, leading to a call stack walk by the CLR. Each method in the call stack's assembly is checked for the required permission, and if any assembly is missing the necessary permission, a security exception is thrown .

ASP.NET utilizes Internet Information Services (IIS) as the hosting environment for web-based applications, allowing developers to target both Web Forms and XML Web Services. IIS and ASP.NET work together as the publishing mechanism, which is vital for deploying and running ASP.NET applications efficiently, providing enhanced performance, manageability, and scalability .

A test plan is crucial in software testing as it defines the strategy and scope of testing, ensuring all aspects of the software are thoroughly evaluated. Key components it must address include software requirements, test objectives, resource allocation, schedule estimation, risk identification, and test criteria. The plan facilitates structured testing to discover defects and ensure the software meets business and technical requirements .

The .NET Framework supports interoperability with non-Microsoft solutions by building on standards such as SOAP for remote procedure calls, XML for data formatting, and WSDL for web services description. These standards promote interoperability, allowing .NET applications to interact seamlessly with diverse systems across varied environments .

ASP.NET is designed with specific features to improve performance in clustered and multiprocessor environments, such as the runtime's ability to closely monitor and manage processes. If a process misbehaves (e.g., leaks or deadlocks), a new one can be created to replace it, maintaining application availability. ASP.NET's compilation model, early binding, and caching services also contribute to its ability to scale and perform under high load conditions .

The .NET Framework's class library, divided into the Base Class Library and the Framework Class Library, supports multi-language development by providing a consistent and unified collection of APIs accessible from any .NET language. The primary namespaces used are System.* and Microsoft.*, which encapsulate various functionalities needed across different applications, thereby enhancing the versatility and efficiency of language-independent development .

The design phase of software development according to Software Project Management principles involves creating models or representations of entities to be built, which encompasses conceptual design, defining project scope and expectations, and the overall project management approach. It includes estimating resources, scheduling, identifying risks, and outlining roles and responsibilities aligned with project goals and objectives .

Operational feasibility for implementing new computerized systems involves assessing the readiness and willingness of user staff to adapt to the system. It's essential to predict and manage user resistance by understanding and addressing concerns, providing adequate training, and demonstrating how the new system aligns with improving their workflow and organization goals .

ASP.NET offers several key advantages over previous web development models: enhanced performance through compiled code and caching; world-class tool support with Visual Studio integration; power and flexibility derived from the common language runtime and .NET class library; simplified tasks (e.g., deployment); and robust security features .

You might also like