A Project Reort

Medical Lab Patient Billing and Inventory Management System [ASP.
NET, C# & SQL-Server 2005]
Profile of Organization
Vision
"Together we create the Enterprises of Tomorrow"
Mission
"To provide world-class Information Technology solutions and services"
Overview
HCL is a leading global technology and IT enterprise with annual revenues of US $ 4.8 billion. The
HCL enterprise comprises of two companies listed in India, HCL Technologies Ltd. and HCL Info
Systems Ltd. It is more than just India's largest selling PC brand. HCL is a world leader in aerospace,
life sciences, the banking sector and BPO. There are many diverse and creative things that are
happening at HCL. Given the growing opportunities in the field, education and training is a natural
extension. Abreast with every change in technology, HCL has set up world class Career Development
Centers.
16-MCA-2006 19-MCA-2006 31-MCA-2006

98
Medical Lab Patient Billing and Inventory Management System [ASP.NET, C# & SQL-Server 2005]
HCL Info Systems is India’s premier information enabling company. Leveraging its 31 years of
expertise in total technology solutions, HCL Info Systems offers value-added services in key areas such
as system integration, networking consultancy and a wide range of support services.
HCL Info Systems is among the leading players in all the segments comprising the domestic IT
products, solutions and related services business, which includes PC’s, servers, networking product,
imaging and communication products.
HCL Info Systems manufacturing facilities are ISO 9001 – 2000 & ISO 14001 certified and adhere to
stringent quality standards and global processes. With the largest installed PC base in the country, four
indigenously developed and manufactured PC brands are ‘Infiniti’, ‘Busybee’, ‘Beanstalk’, and
‘Ezeebee’. HCL Info Systems aims to further leverage its dominance in the PC market. HCL is rated as
Top Players in the PC industry by IDC, and the ‘Infiniti’ line of business computing products is
incorporated with leading edge products from the world leaders such as Intel. A fully integrated and
16-MCA-2006 19-MCA-2006 31-MCA-2006

98
business ready family of servers and workstations, the ‘Infiniti Global Line’ is targeted at medium and
large companies to help them to manage their enterprise-related applications. HCL Info Systems has
considerable dominance in verticals like finance, government, education and research.

To enhance its market reach and strength, HCL has tied-up with global technology leaders, viz.
Microsoft, Oracle, Cisco, Redhat.
Introduction to project
16-MCA-2006 19-MCA-2006 31-MCA-2006

98
The topic, we have selected for our Project work is of a different field and is of great importance to us as
beginner in the field of software and it helped us to learn many things and this learning experience will
help us in a long run of our career. Developing a Web Site was not so easy task; as it requires a lot of
human effort and creativity.
Modern Medical Lab is computerized medical lab where the patient of all the age groups can go under
examination under the specialized doctors using the modern technologies.
Medical Laboratory is very soul of diagnosis making. Better diagnosis does mean better patient care.
Patient Tests are best diagnosis of the patients’ health.
Aim of the Project
16-MCA-2006 19-MCA-2006 31-MCA-2006

98
 Medical Lab Patient Billing and Inventory Management System is developed to automate the
working of Medical Labs and to maintain Test Record.
 Patient Information, Patient Test Information, Staff Information, Patient Report, Tests Information,
Inventory Details, Lab Details and Referring Doctor Details are stored in the database.
 The system enables to generate reports of each test done by the patient on specific date.
 It also maintains the required information of the employees in the Lab.
 It also maintains all the information of all the equipments and chemicals used in the Lab.
 To act System as a Source of information for Laboratory as well as for patients.
 To reduce manual work as much as possible.
 To improve the efficiency of the work which were wasted in keeping records.
 To provide information of registered patients without loss of time.
Scope of the Project
16-MCA-2006 19-MCA-2006 31-MCA-2006

98
Existing System
◦ Existing System is a manual System and all the Process related to the patients and
doctors are stored manually in the form of Files and registers.
◦ Storing all the relevant data about the Test Record, Staff, Stock etc is difficult to
maintain.
◦ Involves time constraint.
Proposed System
o The proposed system wills checks thoroughly for their accuracy of data and whenever
some transaction takes place is valid and correct.
o Provide Web based easy to use interface to the users.
o One of the main advantages of the computerization of the system is that it saves lots of
time, which was previously spending for preparing data files manually can now be used
in some other useful works.
o This system will provide easy record maintenance, queries satisfaction and report
generation.
Security
16-MCA-2006 19-MCA-2006 31-MCA-2006

98
This module controls security and integrity of database in each module with multilevel password that
can be assigned to authorized users by the super user.
 ACCESS CONTROL (Who has the right to access the software)
 AUTHORISATION (Defining rights of an user)
 AUTHENTICATION (Checking who the user is)
 DATA INTEGRITY (Protection of data from modification and deletion)
 DATA SECURITY (Maintain confidentiality of data)
 PASSWORD INTEGRITY (Encryption of passwords)
Problem definition
16-MCA-2006 19-MCA-2006 31-MCA-2006
98
The problem arises when the system gives inaccurate or invalid data. This problem is faced because
of the following reason:
There are lots of transactions made every day and there is always a chance of inaccurate data entry.
Problems of capacity
a queue for a long time for test registration, collecting his/her receipt, test report, test bill and/or any
other information.
There is a big problem of capacity as a large number of tasks are done every day. A Patient has to
wait in.
Few Other Problems
Patient reports cannot be stored forever.
It is very difficult to find the test report of a patient report who has visited the Lab after a long time.
Facilities Available
Visitor Requests, Appointments and Feedback
16-MCA-2006 19-MCA-2006 31-MCA-2006

98
Patient Records
Patient Billing and Test Report Generation
Inventory Management
Employee Records
Employee Attendance
Stock Management
Password Recover
Role and Responsibility
It is the responsibility of the members of the team presented in the paragraphs.
Project Manager (PM)
The PM would undertake periodic project reviews aimed at ensuring that Project, Progress in line with
Project objectives especially those pertaining to quality engineering.
• Supervision for project.
• Ensuring that Project schedules are met.
• Monitoring man power and machine resources.
• Planning for and responding to any contingencies.
• Monitoring quality of program system test.
Team Leader
16-MCA-2006 19-MCA-2006 31-MCA-2006

98
The Team Leader will be responsible for overall coordination and administration of the Project. His
responsibilities would include:
• System analysis
• System Design.
• Adherence to standards.
• Coordination of development work.
• Interface between modules.
Module Leader/Team Members/Programmers
These professionals would provide support in the areas of:-
• System Design
• Program Development.
• System Testing
• Program Coding.
• System Software.
• Monitoring and Project Review
• Assistance in system Testing.
• Prepare Documentation.
Team Structure
16-MCA-2006 19-MCA-2006 31-MCA-2006

98
The constituted team with inter-disciplinary strengths as required for the completion of the project is
shown in the following chart. It would consist of an appropriate mix of an HOD/PM (Internal Project
Guide), Project Leader, Software professional and Quality Coordinator.
TEAM LEADER (External Project Guide)
Rajinder Kr. Chitoria
Program Design and Development
(Asief Showket Wani, Sajad Ahmed Shah, Majid Ahmed Malik)
Monitoring and Project Review
(Asief Showket Wani, Sajad Ahmed Shah, Majid Ahmed Malik)
Programmer/Module Programmer/Module Programmer/Module
Testing Testing Testing
(Asief Showket Wani) (Sajad Ahmed Shah) (Majid Ahmed Malik)
Gantt Chart
16-MCA-2006 19-MCA-2006 31-MCA-2006

98
The Gantt chart is a simple time charting tool was developed by Henry L. Gantt in 1917. It is popular
for project scheduling and progress evaluation. Like Pert char, the Gantt chart is graphical. They are
easy to learn and use. Within the Gantt chart the horizontal axis represents time and tasks are listed
vertically in left hand column.
As a sequence of the inputs, a timeline chart, also called a Gantt Chart, is generated. A Gantt Chart can
be developed for the entire project. Alternatively, separated it depicts a part of a software project
schedule that emphasizes the concept scooping task for a new word processing software project. All
project tasks (for concept scooping) are listed in the left hand column. The horizontal bars occur at the
same time on the calendar, task concurrency is implied. The diamonds indicate milestones.
Once the information necessary for the generation of the Gantt Chart has been input, the major of
software project scheduling tools produce project tables a tabular listing of all project tasks, their
planned and actual start and end dates, and a verity of related information. Used in conjunction with the
Gantt Chart project tables enable the project manager to track progress
Our Project Gantt chart will be formulated given below:
16-MCA-2006 19-MCA-2006 31-MCA-2006

98
1. Requirement
Analysis
2. Design Phase
3. Coding
4. Testing
5. Finalizing
20 30 1 20 31 1 20 31 1 20 28 1 20 31 1 14
Feb Mar April May June July
GENERAL DIAGRAM FOR DEVELOPING A SYSTEM

16-MCA-2006 19-MCA-2006 31-MCA-2006
98
NEED
Request to develop a system
Recognition of Need
Feasibility Study
Analysis
Design
Implementation
Maintenance
Requirement Analysis
16-MCA-2006 19-MCA-2006 31-MCA-2006

98
The initiation of a system (or project) begins when a business need or opportunity is identified. A
Project Manager should be appointed to manage the project. This business need is documented in a
Concept Proposal. After the Concept Proposal is approved, the System Concept Development Phase
begins.
Once a business need is approved, the approaches for accomplishing the concept are reviewed for
feasibility and appropriateness. The Systems Boundary Document identifies the scope of the system and
requires Senior Official approval and funding before beginning the Planning Phase.
On Spot Observation
As the details are gathered than we study the requirements, data to identify, features the new system
should have, including both the information the system should produce and operational features such
processing controls, response times, and input and output methods. We visited few Medical Laboratories
to understand the actual online process.
Fitness Labs (Medical Lab in Noida) has given us the great opportunity to Analyze administrative and
staff details, so as to develop system accordingly.
Laboratory management provided us all necessary information such as manual registration of patients,
registration of staff, patient test reports, billing and attendance of staff etc.
They provided necessary answers to our questions. Staff of Fitness Lab Noida (U.P) is Supportive,
Coordinating and active.
Fitness Labs we have visited several Medical Laboratories on the internet and get help from them.
Reviewing Record
16-MCA-2006 19-MCA-2006 31-MCA-2006

98
Before starting on the development of system we had to look the previous recording procedures done all
manually. Previously it was done manually and their records are maintained in the form of files and
registers.
Existing System
Existing System is a manual System and all the Process related to the patients and doctors are stored
manually in the form of files and registers.
Requirements
 Modern Medical lab will provide appointments to visitors and supports visitor feedback.
 Modern Medical lab will support registering patients.
 Modern Medical lab keeps track of each patient’s record.
 Employees can search for patients Records.
 Registered Patients can access their personal records (tests reports, bills etc).
 Modern Medical lab maintains the list of doctors/technicians in the Laboratory.
 Support for attendance of employees.
 Support for Stock (equipments and regents) managements
 Support for Inventory managements
Process Logic
16-MCA-2006 19-MCA-2006 31-MCA-2006

98
First of all a person comes to the medical laboratory. The Person registers him/her self to perform some
medical tests. To perform such tests a registration number and a slip is issued to the person which is
stored in the registration module of the system. Later the person collects his/her test report by paying the
specified test bills. Staff database is maintained and regular attendance of staff available on duty is
performed. Stock maintains the available equipment or regent details. Search option for search of patient
information, test reports, bills and staff information search by providing id number.
System development
To understand the concept of system development, we need to recognize that a candidate system has a
life cycle, just like a living system or a new product. System analysis and design are keyed to the system
life cycle.
System development has various stages. The System analyst must progress from one stage to another
methodologically, answering key questions and achieving results in each stage.
Design Phase
16-MCA-2006 19-MCA-2006 31-MCA-2006

98
The most creative and challenging phase of the system life cycle is system design. The term design
describes a final system and the process by which it is developed. It refers to the technical specifications
that will be applied in implementing the candidate system.
The first step is to determine how the output is to be produced and in what format. Samples for the
output (and input) are also presented.
The second step is input data and master files (data base) have to be designed to meet the requirements
of the proposed output. The operational (processing) phases are handled through program construction
and testing including a list of the programs needed to meet the system’s objective and complete
documentation. Finally, details related to justification of the system on the user and the organization are
documented and evaluated by management as a step toward implementation. To design the system we
must note the following points:
 To identify the Software Components which satisfy the System Design.
 To design and document the Software Components and their linkage.
In this component the software components and relevant interfaces such as, interactions with
existing internal and external systems, network connections, standard input and output formats are to be
identified.
After completing the requirement study and documentation, it is time to design the software based on
the requirements. It is easy to start coding without any design and we may end up developing a product
which our customers like. But it may not be easy to maintain. Customers may keep changing their mind.
Only after seeing the product, they may say 'we want this to behave in a different way', and it is very
hard to say 'NO' to a customer. First step is identifying all the features that we are going to implement in
16-MCA-2006 19-MCA-2006 31-MCA-2006

98
the software. The requirements document is a good guide in identifying the features. According to the
requirements specification, we need to develop the following features in the system.
 Visitor Feedback and Appointments
 Registration of Patients
 Patient Information Management
 Patient Tests and Bill Details
 Search for Patients Information
 Staff Information System
 Stock Information System
 Inventory Management System
Registration
This feature allows adding a new patient’s data in the system. We should be able to store at least the
basic information like Name, Address, Sex, Date of Birth, and contact number etc.
Patient Information Management
This feature allows keeping track of Patients information, so that we can access particular patient’s
information at any time. For this purpose we have to specify a unique entity such as Registration
Number of patient.
16-MCA-2006 19-MCA-2006 31-MCA-2006

98
Search for Patients Information
With this feature employees of the medical laboratory should be able to search for the particular Patients
record, if the Registration number is provided to them. The system should be able to search for the full
(complete) information of the patient which is entered at the time of Registration.
Storage of Information
This feature allows storing of information in a particular location so that stored information can be
accessed later by the Users. The system should be able to store the information of Patient as discussed
blow:
1. Registration Number for the Patient.
2. Name of the Patient.
3. Guardian.
4. Sex of the Patient.
5. ADDRESS
a.) City.
b.) State
c.) Pin Code
6. Date of Birth
a.) Day
b.) Month
c.) Year
7. Marital Status
16-MCA-2006 19-MCA-2006 31-MCA-2006

98
Married or Single
8. Contact Number
9. Registration Date
System Design
Before going to design a system one should know what system means to be. Basically system is an
integrated collection of components that satisfy functions necessary to achieve the system’s goals and
which have relationships to one another that give cohesion to the system and define its structure.
Basically system consists of three processes these are:
1. Input
2. Processor
3. Output
All these processes are done by programmer, where he collects the input requirements from the user, he
designs the input structure, and for obtaining output, user don’t know the type of process which had
gone through in the software . Conversion of input into output is called as process. We had gone through
the process between the process, between the input and output known processing process.
Inputs
16-MCA-2006 19-MCA-2006 31-MCA-2006

98
Inputs are basically data fed into the system or the database. Inputs are entered by the Users who are
using the system with the help of keyboard and mouse.
o Visitor Information
o Appointment Information
o Patient Registration Information
o Staff Registration Information
o Name of the Tests
o Test Results
o Bill Details
o Staff Attendance
o Monthly Staff Salary
o Stock Availability.
Outputs
Report module produces views, which can act as management information system. Some of them as
follow:
o View Visit Information
o View Patient Details.
o View Patient Test Status
o View Patient Test Details
o View Patient Bill Details
16-MCA-2006 19-MCA-2006 31-MCA-2006

98
o View Staff Details
o View Staff on Duty
o View Staff Salary Details
Main Actors
In medical lab patient billing and inventory management system there are mainly four actors:
1.) Visitor
2.) Administrator
3.) Employees
a.) Doctors
b.) Technicians
4.) Patient
Visitor:
Visitor is a person that accesses the site by using the website address. The various facilities available to
the visitor are:
1. Visitor can browse the site.
It means that a visitor can view all the basic information that is on the site but with certain
limitations until he/she gets registration number.
16-MCA-2006 19-MCA-2006 31-MCA-2006

98
2. Visitor can search for tests available, facilities provided, test charges etc.
3. Visitor can get the appointment by filling the visitor form.
4. After filling the visitor form, visitors can login to the system by providing E-mail ID as login ID
and Visitor ID as Password so as to check appointment details, provide feedback etc.
5. Visitor is not a registered member or does not have any agreement thus he/she is provided access
to the site with restrictions. Thus to avail all the services he/she has first to register by filling the
Visitor Appointment registration form provided on the home page.
Administrator:
An administrator is a person having all the authorities and responsibilities to manage and oversees the
whole resources related to the application.
1. Administrator can login to his member area by supplying unique identification and
password.
2. Administrator has the power to confirm or disconfirm the registration of the
patient/employees.
3. Administrator is responsible for managing the resources such as equipments, regents
and
labs.
4. Administrator has the authority to change the services which appears on the members
area or the home page .
16-MCA-2006 19-MCA-2006 31-MCA-2006

98
5. Administrator has the authority to cancel the registration of a member depending upon
certain conditions.
a. If the person has never logged for 1 year
b. if the persons date of birth is <1900
6. Administrator is responsible to keep track of all the resources specially the registered
visitors, patients, employees and to help them whenever they need in the form of quires.
There are also feed back forms which helps the administrator to remove any flaw or to
improve the efficiency of the application and the maximum utilization of the resources.
7. Administrator can access vital information such as login information of all the users of
the system and modify it if necessary.
8. Administration can check feedback provided by the visitors and contact them.
9. Administrator can make the attendance of all employees on daily basis.
10. Administrator can pay salary for all employees on monthly basis.
11. Administrator can generate various reports such as billing reports, salary reports and
inventory reports.
12. Administrator can change or modify any service available without any permission.
13. Logout: Administrator can Logout form his member area to Login Screen.
14. Home Page: Administrator can Logout form his member area to Home Page.
16-MCA-2006 19-MCA-2006 31-MCA-2006

98
Employees:
Employees are the persons who have been registered as the members and they are provided with the
unique ID and PASSWORD by the administrator. Employees are provided with the space to login to
their member area by supplying the member ID and the PASSWORD for his unique identification in
order to protect unauthorized users to access the member area. Once employee enters to his/her member
area he/she can avail various services provided by the administrator:
1. Employee can update his/her profile, by changing his Password, Phone number, Email
address, Mailing address, Pin code etc.
2. Employees can check visitors and can fix appointments, without the administrator
permission.
3. Employees can provide registration to patients.
4. Doctors/Technicians can search for patient tests; perform any patient test and prepare test
reports.
5. Doctors/Technicians can view any test result they performed for future reference.
6. Employees can generate patient bill reports.
7. Employees can request for any stock item required for test purpose.
8. Employees can check for their salary.
9. Logout: Employer can logout form his member area to Login Screen.
10. Home Page: Employer can logout form his member area to Home Page
16-MCA-2006 19-MCA-2006 31-MCA-2006

98
Patient:
Patients are the persons which are provided with registration number to carry out their tests. With the
help of user ID and password patients can access the medical reports online anywhere if needed.
Patients can access test reports, bills and there personal information.
1. Patients get the registration number.
2. Can access there member area to check medical information.
3. Logout: Patients can Logout form his member area to Login Screen.
4. Home Page: Patients can Logout form his member area to Home Page.
16-MCA-2006 19-MCA-2006 31-MCA-2006

98
Data Flow Diagrams

In a software system, information is modified as a series of transformations. Each process
transformation models and changes the data in a specific way. The entire Software can be represented as
a series of these transformations, which are applied in conjunction to one another.
Definition:
A Data Flow Diagram (DFD) is essentially a graphical technique that depicts informational flow and the
transforms that are applied as data moves from the input to the output. A Data Flow Diagram is also
known as a data flow graph or a bubble chart.
Need for a Data Flow Diagram
The Data Flow Diagram is essentially used to represent a system at any level of abstraction. The DFD
may be portioned into levels that represent increasing functional as well as information flow modeling.
Some of the components of the DFD’s are:
External Entity: A producer or consumer of information that resides outside the bounds of the system
to be Modeled, generally represented as rectangle.
Process: A transformer of information that resides within the bounds of the System to be modeled,
generally represented as a circle.
Data Object: A data object, generally represented as an arrow indicating direction Flow.
Data Store: A repository of data that is to be stored for use of one or more Processes; may be as
16-MCA-2006 19-MCA-2006 31-MCA-2006

98
simple as a buffer or queue sophisticated as a Relational database. Generally represented
as a set of two Parallel lines or an open rectangle.
Symbols Used in DFD’s
1. External entity:
USER
2. Process: Process
Order
Direction flow of data

3. Data Object:
Data Base
5. Data Store:
16-MCA-2006 19-MCA-2006 31-MCA-2006

98
Data Flow Diagram of Project

A Data Flow Diagram used in this Project to represent interaction between Users and the Data Base.
Administrator
Response Controls
Patient Employee
Response
Registration
Manipulates
Request
0.0
Access
Response
MLPBIM Visitor
Response
CONTEXT LEVEL DIAGRAM of Medical

Lab System
16-MCA-2006 19-MCA-2006 31-MCA-2006

98
Administrator
Request for
2.0
Billing Data
View
Billing Bill Details
Login
Failed
Reads
Login Details
Billing
Request for
System
3.0
Inventory
1.0 Writes
Lab
Login Inventory Stock Data
Process Process Store
Reads
RequestAdd/update Writes
Tests Request to
manage Staff 4.0
Staff Data Store
Managing
Staff
Reads
Reads
5.0
Test Data Store Add/Updat

e Tests
writes
Level-1 Diagram of Medical Lab System
16-MCA-2006 19-MCA-2006 31-MCA-2006

98
Employee
Login Failed Login Details
1.0
Login Available
Tests
Patient Data Test Details

Stores Patient
1.2
Details Test Data Stores Requested Tests
1.1 Check TTestTesults
Patient Patient
Test Test
Details Registratio
n Process Availabi Details
lity
Test Request
Stores Test
Results
Patient Test
Result 1.3
Retrieves Test Testing

&Value Procedu
Test
re
Details
Generate Report
Patient
1.4 Writes
Report/Bill
Billing
Generate Bill
Procedu Details
re Reads
16-MCA-2006 19-MCA-2006 31-MCA-2006

98
Level 1 Diagram For Medical Lab
Patient
Logindetails
Login Failed
Required Info 1.0
Login
Process
Requests for
details
Retrieves Retrieves
1.1
Patient Data
Store View Bill Bill Details
Details
Retrieves
Patient Test Result
Level 1 Diagram of Medical Lab System
16-MCA-2006 19-MCA-2006 31-MCA-2006

98
Visitor
Login ID Login Failed
Reads 1.1 1.0 Request for

Visitor
Details Appointme
writes nt Process Appointment Login
Feedback
Details
Feed Back
Stores feedback
1.2
Feedback
Process
16-MCA-2006 19-MCA-2006 31-MCA-2006

98
From Process
3.0 From Process 3.0
From Process 3.0
Reads Data
Stock Data 3.1
store
Add/Delete
Updates Stock
Reads
Reads Data
3.2
Checking
Update Quantity
Reads Data
3.3
Maintenanc
e of Stock
Update
16-MCA-2006 19-MCA-2006 31-MCA-2006

98
Level-2 Diagram of Medical Lab System (For Billing)
USER INTERFACE DIAGRAMS

Visitor Appointments or Feedback
Interface diagram shows the registration of a visitor and access to visitor area.
Request
Enter details of a
Visitor Appointment Form
Visitor
Query
Get Registration
Get Appointment Details/Feedback

MLPBIMS
Enter E-mail ID and
Password
Visitor Information Search
16-MCA-2006 19-MCA-2006 31-MCA-2006

98
Registration of a Patient
Interface diagram to show how a registration of a patient is done in Medical Lab Patient Billing and
Information Management System (MLPBIMS)
Request Registration of a Enter details of a

User
Patient Patient
Patient info
management
Get Registration
MLPBIMS
REGISTRATION OF A PATIENT
16-MCA-2006 19-MCA-2006 31-MCA-2006

98
Information Search of Existing Patients
Interface Diagram to show how an employee get access to patient records in Patient Billing and
Information Management System.
Query
Record of an Enter Reg. number
Employee
existing Patient of a Patient
Patient info
management
Get Record
MLPBIMS
RECORD OF AN EXISTING PATIENT
16-MCA-2006 19-MCA-2006 31-MCA-2006

98
Naming Conventions and Database Design
Naming Convention:-
• As the project size grows, so does the complexity of recognizing the purpose of the
variables. Thus the variables were given meaningful names, which would help in
understanding the context and the purpose of the variable.
• The function names are also given meaningful names that can be easily understood
by the user.
Naming Conventions for the Creation of Database Tables
Item Naming conventions
Classes Class names should clearly indicate the entity that it represents.
For example, the name of the class that represents a Customer
should be named ‘ClassCustomer ’.

Objects Object names should begin with ‘obj’.
Variables Integer – intVarName
Decimal – dVarName
String – strVarName
Boolean – bVarName
16-MCA-2006 19-MCA-2006 31-MCA-2006

98
Controls Label – lblControlName
Text Box- tbControlName
Button – btnControlName
List Box – lbControlName
Drop Down List - ddlControlName
Radio Button – rbControlName
Check Box List – cblControlName

Files File names should clearly indicate the kind of data that they store.
For example, the name of the file containing the definition of the
Customer class should be Customer .vb.
16-MCA-2006 19-MCA-2006 31-MCA-2006

98
p a t ie n t _ t e s t _ r e s u lt p a t ie n t _ t e s t _ d e t asils
t o c k _ e q u ip m e n t _ d e t a ils
s t o c k _ is s u e _ d e t a ils
p id
p id
e _ s t o c k _ id s _ is s u e _ id
s id
tes t_ nam e e _ id
t e s t _ id s t a f f _ id
s a la r y _ d e t a ils s t a f f_ a t t e n d a n c e tes t_ date e _ na m e
e _ s t o c k _ id
in v e s t ig a t io n
tes t_ s tatus e _ de s c m _ s t o c k _ id
t e s t _ r e s ult
s id e _ c o m p a ny
s id e _ id
n o r m a l_ v a lue s
ac c _ n o e_ c o s t e _ q ua nt it y
s atte ndanc e_ s ta tus d e s c r ipt io n
pa s s _ k e y t o t a l_ c o s t m _ id
s t a f f_ d e t a ils p r e steensttda
_ dt ee t a ils p a t ie n tt_eds et _t af eils
e
s t a f f_ s a la r y _ d e t a ils
e _ qu a nt it y
s a la r y m _ q u a nt it y
s tat us t o t a l_ qu a n t it y tes t_ nam e

v is it o r _ d e t a ils
a v a il_ qu a n t it y
is s u e _ d a t e
e _ pu r c h a s e _ d a t e
s t o c k _ m e d ic in e _ d e t a ils
e _ e x p ir y _ d a t e
ac c _ no s id t e s t _ id p id
la b _ d e t a ils
s nam e inv e s t ig a t io n p na m e
s a la r y
r e c y c le _ t e s t
s sex n o r m a l_ v a lu e s p gu a r d ia n
in c e n t iv e s
v _ id
s m a r it a l_ s t a t u s la b _ n o psex
t s a la r y
v _ nam e
s dob tes t_ f ee p m a r it a l_ s t a t u s
date
v _ c o nt a c t
s t y p ep a t ie n t _ b ill_ d e t a ils p do b
m _ s t o c k _ id v _ e m a il
s s p e c iliz a t io n pstate
u s e r lo g in m _ id v _ p u r po s e
s s tate p c it y
m _ na m e v_ tes ts
s c it y p z ip
m _ de s c v _ date
s z ip la b_ n o pc ontac t_ no
m _ c o m p a ny s t a f f _ id
s c o nt a c t la b_ n a m e p e m a il_ id
p id m _ cost dr_ nam e
s e m a il la b_ lo c a t io n pref _ dr_ na m e
s id t o t a l_ c o s t m o b ile
s doj ps tatus
t e s t _ id m _ qu a nt it y la b _ lo c a t io n
preg_ date
inv e s t iga t io n t o t a l_ qu a n t it y v _ a p po in t _ d a t e
p gu a r d ia n t y p e
t e s t _ r e s ult a v a il_ qu a n t it y s tatus
n o r m a l_ v a lue s m _ pu r c h a s e _ d a t e f e edbac k
b illid
d e s c r ip t io n p id m _ e x p ir y _ d a t e
tes t_ f ee us e r id s id
d e le t e _ b y us e r na m e t es t _ na m e
d a le t e _ d a t e lo ginp a s s w o r d t o t a l_ c h a r ge s
lo ginr o le e x t r a _ c ha r g e s
s e c ur it y q u s e t io n grand_ tota l
s e c ur it y a n s w e r b ill_ d a t e
DATABASE RELATIONSHIP DIAGRAMS
16-MCA-2006 19-MCA-2006 31-MCA-2006

98
System Implementation And Testing
System implementation is the stage when the user has thoroughly tested the system and approves all the
features provided by the system. The various tests are performed and the system is approved only after
all the requirements are met and the user is satisfied.
The new system may be totally new; replacing an existing manual or automated system, or it
may be a major modification to an existing system. In either case, proper implementation is essential to
provide a reliable system to meet organizational requirements. Successful implementation may not
guarantee improvement in the organization using the new system (that is a design question), but
improper will prevent it.
Implementation is the process of having systems personnel check out and put new equipment into use,
train users, install the new application and construct any files of data needed to use it. This phase is less
creative than system design. Depending on the size of the organization that will be involved in using the
application and the risk involved in its use, systems developers may choose to test the operation in only
one area of the firm with only one or two persons. Sometimes, they will run both old and new system in
parallel way to com-pare the results. In still other situations, system developers stop using the old
system one day and start using the new one the next.
Aspects of Implementation
The two aspects of implementation are:
• Training Personnel
• Conversion Procedures
16-MCA-2006 19-MCA-2006 31-MCA-2006

98
TRAINING
Even well designed and technically elegant systems can succeed or fail because of the way they
are used. Therefore the quality of the training received by the personnel involved with the system in
various ways helps or hinders, and may even prevent, the successful implementation of an information
system.
Since, Human Resource Recruitment Process is web-based and user friendly, not much effort
was required in training process.
CONVERSION:
Conversion is the process of changing from the old system to the new system. There are two
methods of handling systems conversion:
• Parallel Run
• Immediate cut-off
Parallel Run
In this approach, the old system and the new system are used simultaneously for some period of
time so that the performance of the new system can be monitored and compared with that of the old
system. Also in case of failure of the new system, the user can fall back on the old system. The risk of
this approach is that the user may never want to shift to new system.
Immediate cut-off
In this method, the use of the old system ceases as soon as the new system is implemented and
bought in to palace. The old system becomes redundant from the day of implementation of the new
system. There is the high risk involved in this approach if the new system is not tested rigorously. This
16-MCA-2006 19-MCA-2006 31-MCA-2006

98
is because of the fact that if the new system fails, then there will not be anything to fall back upon. The
advantage of this approach is that both the systems need not be used simultaneously.
1 Implementation Tools
The project was implemented using ASP.NET server pages, HTML, ASP.NET beans. The
implementation work was carried out in Windows XP/2000 server platform.
1) C#.Net and Asp.Net
2) SQL Server 2005
1.1 Coding
This means program construction with procedural specifications has finished and the coding for
the program begins:
• Once the design phase was over, coding commenced.
• Coding is natural consequence of design.
• Coding step translate a detailed design representation of software into a programming
language realization.
• Main emphasis while coding was on style so that the end result was an optimized code.
The following points were kept into consideration while coding:-
1.2 Coding Style
The structured programming method was used in all the modules the project.It incorporated the
following features
• The code has been written so that the definition and implementation of each function is
contained in one file.
• A group of related function was clubbed together in one file to include it when needed and
save us from the labour of writing it again and again.
16-MCA-2006 19-MCA-2006 31-MCA-2006

98
1.3 Naming Convention:-
• As the project size grows, so does the complexity of recognizing the purpose of the variables.
Thus the variables were given meaningful names, which would help in understanding the context
and the purpose of the variable.
• The function names are also given meaningful names that can be easily understood by the user.
1.4 Indentation
Judicious use of indentation can make the task of reading and understanding a program much
simpler. Indentation is an essential part of a good program. If code id intended without thought it will
seriously affect the readability of the program
• The higher-level statements like he definition of the variables, constants and the function are
intended, with each nested block intended, stating their purpose in the code.
• Blank line is also left between each function definition to make the code look neat.
• Indentation for each source file stating he purpose of the file is also done
16-MCA-2006 19-MCA-2006 31-MCA-2006

98
Form Design
Form Name Form Type Description Table/Query Used
Home.aspx Web Form Displays the Home Page for the
application.
Login.aspx Web Form Accepts user ID and password. userlogin
Allows a maximum of 3
attempts. If in all 3 attempts, a
wrong user name and password
is specified, the application is
terminated. On entering the
correct user ID and password,
the person gets logged into the
system.
ForgotPassword.aspx Web Form An important service provided
by the system to recover
password based on certain
conditions so as to gain access
to the system.
ChangePassword.aspx Web Form After logged in to the system
the user can change his/her
password for more security
purpose.
Visitor.aspx Web Form Allows a visitor to search visitor_details
16-MCA-2006 19-MCA-2006 31-MCA-2006

98
particular information from the
system and get appointment or
to provide feedback to the
Administrator.
VisitResponse.aspx Web Form
AdministratorHome.aspx Web Form Administrator Super user of the staff_details,
System. Various important staff_attendance,
tasks such as creates and salary_details,
deletets Users(Employees), staff_salary_details,
updates employee profile, test_details,
employee attendance, manage stock_equipment_details
stocks for the tests, manages ,
labs and so on… stock_medicine_details,
lab_details
EmployeeHome.aspx Web Form Allows an employee to view his Staff_details,
profile, perform various test_details,
departmental tasks like parient_bill_details,
performing tests, bill stock_issue_details
generation, test report
generation and issuing an item
from stock.
PatientHome.aspx Web Form Allows a patient to view. patient_test_details,
16-MCA-2006 19-MCA-2006 31-MCA-2006

98
previous test reports and bill patient_test_result,
reports patient_bill_details
StaffRegistration.aspx Web Form Allows Administrator to staff_details
Register a new Employee,
Search existing employee
details, update employee record,
view all employees and print
existing employees report
PatientRegistration.aspx Web Form Allows Employees to Register a patient_details
new Patient, Search existing
patient details, update patient
record, view all patients and
print existing patient report
AdditionalUserInfo.aspx Web Form Allows userlogin
Administrator/Employees to
add additional information such
as Login Name, Password and
Security question, Answer
LabDetails.aspx Allows Administrator to add,
delete or to modify any lab
details.
TestDetails.aspx Web Form Allows Administrator to add,
16-MCA-2006 19-MCA-2006 31-MCA-2006

98
delete or to modify any test
details.
PatientTestDetails.aspx Web Form Allows Employees to add tests
for a registered patient, test
status remains UnDone until
tests are performed.
PatientTestResult.aspx Web Form Allows doctors/technicians to
perform tests for patients and to
generate test report.
PatientBillDetails.aspx Web Form After all tests for a patient are
done Receptionist are able to
generate bill for patient
StaffAttendance.aspx Web Form Allows Administrator to mark
attendance of all employees on
daily basis.
StaffSalaryDetails.aspx Web Form Allows administrator to create
salary account for an employee
and to fix salary or to modify
the monthly salary of an
employee.
StaffSalary.aspx Web Form Based on salary account
number the employees can
16-MCA-2006 19-MCA-2006 31-MCA-2006

98
check their salary details.
StockEquipmentDetails.aspx Web Form Only Administrator can make
order for the purchase of new
equipment or re-order existing
equipments. Administrator can
also remove expired equipments
from stock.
StockMedicineDetails.aspx Web Form Only Administrator can make
order for the purchase of new
regent/medicines or re-order
existing regent/medicines.
Administrator can also remove
expired regent/medicines from
stock.
StockIssueDetails.aspx Web Form Only doctors/technicians can
issue equipments or regents or
both for any type of test
depending on their requirement.
16-MCA-2006 19-MCA-2006 31-MCA-2006

98
Validation to be performed
• Form: Logon
• The user ID and password should exist in the userlogin table.
• If number of attempts is less than 3, allow a user to re-enter the user ID and password, otherwise
terminate the application.
• Form: Visitor
• The visitor form will be used for a visitor for appointments with the doctors and to provide
feedback.
• Visitor can check for appointment details by logging to visitor account.
• Visitor will be contacted by the administrator for complain mentioned in feedback.
• Only administrator is able to view feedback from visitors.
• Form: Administrator
• Role must be an Administrator besides valid user ID and password.
• Vital information such as login information of all users will available only to administrator.
16-MCA-2006 19-MCA-2006 31-MCA-2006

98
• Responsible for Creation of employee’s salary accounts.
• No other employee should gain access to Administrator area.
• Form: Employee
• Employee’s entry should be in the staff_details table.
• Employee should enter valid Role, User ID and Password.
• Form: Patient
• Patient’s entry should be in the patient_details table.
• Patient should enter valid Role, User ID and Password.
16-MCA-2006 19-MCA-2006 31-MCA-2006

98
Reports Design
Report Name Report Type Description Tables/Query Used
Patient Detailed Crystal Report (pull Displays the details about all the patient_details
Report method) Patients
Bill Report Crystal Report (pull Displays the details about all tests patient_bill_details
method) that are performed on the patients
Crystal Report (pull Displays the detailed information staff_details

Staff
16-MCA-2006 19-MCA-2006 31-MCA-2006

98
method) of Laboratory Staff.

Information
Crystal Report (pull Displays the details about all the
Salary Report staff_details
method) employee of the lab.
Equipments Crystal Report (pull Keeps Record of All Purchased/In stock_equipment_details

Report method) use/Expired Equipments.
Medicine Crystal Report (pull Keeps Record of All Purchased/In stock_medicine_details

Report method) use/Expired Medicines/Regents
Stock Items Crystal Report (pull Keeps Record of All Issued stock_equipment_detail,
Issue Report method) Equipments/Regents stock_equipment_detail,
stock_issue_details
16-MCA-2006 19-MCA-2006 31-MCA-2006

98
Test Report and Test Procedure Review Checklist
# Path Input Output Actual Result

Form: Login
1. If a wrong user name Any invalid An error message An error message
and password is user name and
entered, an error password
message should be
displayed.
2. If in all 3 attempts a Any invalid An error message An error message in first two
wrong user name and user name and in first two attempts. Third time, a message
password is specified, password, attempts. Third “Unauthorized access.
an error should be then click the time, a message Aborting…”
displayed and the Login button “Unauthorized
application should be three times access.
terminated. Aborting…”
16-MCA-2006 19-MCA-2006 31-MCA-2006

98
3. If a valid user name , User Name: Home page Modern Medical Lab Form
password andpassword E005
is provided, it should Password:

display the home page pass
depends upon the role.
Form: visitor
1. visitor Form: The Clisk on Welcome message, Appointment date will be given to
visitor enter his “RegisterME” visitor

Select the tests.
personal detials. button in the
visitor form
button
Form:Adminstrator
1. Adminstrator Form: Enter all and Welcome message Home page for adminstartor
Valid values for the click the login
user id,password,role button
“staff_id”,
“adminpassword”,
“Admin”
Form:Employee
1. Employee Form: Valid Enter any Error – “Invalid Error – “Please Enter valid
16-MCA-2006 19-MCA-2006 31-MCA-2006

98
values for the user other valuel user Re-enter” Details”
id,password,role and click the
“staff_id”, login button
“staffpassword”,
“Employee”
2. Employee Form: Valid Enter all the Welcome message
values for the user valuel and
id,password,role click the login
“staff_id”, button
“staffpassword”,
“Employee”
Form:Patient
1. Patient Form: the Enter all the Welcome message Home page for patient
patient should have valuel and
been registered,and click the login
should have button
userid,password and
role given
Maintenance and Evaluation
16-MCA-2006 19-MCA-2006 31-MCA-2006

98
Maintenance or enhancement can be classified as: -
• Corrective
• Adaptive
• Perfective.
Corrective maintenance means repairing processing or performance failures or making changes
because of previously uncorrected problems or false assumptions.
Adaptive maintenance means changing the program function.
Perfective maintenance means enhancing the performance or modifying the program(s) to
respond to the user’s additional or changing needs.
Maintenance is actually the implementation of the post implementation review plan.
As important as it is, many programmers and analysts are reluctant to perform or identify
themselves with the maintenance effort. There are psychological, personality and professional reasons
for this. In any case, a first class effort must be made to ensure that software changes are made properly
and in time to keep the system in tune with user specifications.
Maintenance is costly. One way to reduce maintenance costs is through maintenance
management and software modification audits. Software modification consists of program rewrites
system level updates, and re-audits of low ranking programs to verify and correct the soft spots.
The outcome should be more reliable software, a reduced maintenance backlog, and higher
satisfaction and morale among the maintenance staff.
In project, care has been taken towards maintenance; Loop Holes can be eradicated from the
system from time to time according to changing requirements with lesser cost.
EVALUATION
16-MCA-2006 19-MCA-2006 31-MCA-2006

98
The evaluation phase ranks vendor proposals and determines the one best suited, Evaluation of
the system is performed to identify its strengths and weaknesses. The actual evaluation can occur along
any of the following dimensions:
 Operational Evaluation: Assessment of the manner in which the system functions,
including case of use, response time, overall reliability and level of utilization.
 Organizational Impact: Identification and measurement of benefits to the organization in
such areas as financial concerns, operational efficiency and competitive impact.
 User Manager Assessment Evaluation of the attitudes of senior and user manager within
the organization, as well as end-users.
 Development Performance: Evaluation of the development process in accordance with
such yardsticks as overall development time and effort, conformance to budgets and
standards and other project management criteria.
Testing
16-MCA-2006 19-MCA-2006 31-MCA-2006

98
Testing focuses on the logical internals of the software, ensuring that all the statements have
been tested on the functional external, that is, conducting tests using various test data to detect errors
and ensure that defined input will produce actual results that agreed with required results. It is the major
quality control measure used during software development.
It uncovers the errors introduced:
o During Coding
o During other previous phases like: Requirement Analysis and Designing
Levels of Testing
1. Unit Testing
2. Integration Testing
3. System Testing
4. Acceptance Testing
5. Regression Testing
Unit testing (First level of testing):
Different modules are tested against the specifications produced during the design for the
modules. Unit testing is essentially for verification of the code produced during coding phase. Its main
goal is to test the internal logic of the modules, typically done by the programmer of the module. Main
focus in this testing is testing the code.
Integration testing:
16-MCA-2006 19-MCA-2006 31-MCA-2006

98
Many unit tested modules are combined into sub systems and tested. Hence, the emphasis is on
testing interfaces between modules. This testing activity can be considered testing the design.
System testing:
The entire software system is tested. The reference document for this process is the requirement
document. Its goal is to see if the software meets its requirements.
Acceptance testing:
This is the validation activity performed with realistic data of the client to demonstrate that the
software is working satisfactorily. Here, testing focuses on the external behavior of the system.
Regression testing:
This test is performed when some changes are made to an existing system. Changes are made to
“Upgrade” the software by adding new features and functionality. Modified software needs to be tested
to make sure that the new features to be added to do intended work.
Output
The final output of the testing phase is the Test report and the Error report. Test report contains the
set of test cases and the result of executing the code with these test cases.
Error report describes the errors encountered and the action taken to remove the errors.
Benefits of testing
• Coordinate work efforts (reduces duplicate work).
• Consistent definition (reduces confusion \ambiguity).
• Allows protocols (specific terms\methods).
16-MCA-2006 19-MCA-2006 31-MCA-2006

98
SOFTWARE AND HARDWARE REQUIREMENTS

SOFTWARE PLATEFORM
Operating system Windows Xp Professional
Front End ASP .Net, VB .Net, C Sharp
Back End SQL Server2005
Others MS-Word, Adobe Flash Player, Camtesia
Camcoder
HARDWARE RESOURCES
Hard Disk 20 GB or Higher Capacity
RAM 500 MB or Higher capacity
Processor Pentium-IV or above
Monitor 15 inch Colored or VGA
Others DVD-COMBO Drive
Project Screen Shorts

16-MCA-2006 19-MCA-2006 31-MCA-2006
98
16-MCA-2006 19-MCA-2006 31-MCA-2006

98
16-MCA-2006 19-MCA-2006 31-MCA-2006

98
16-MCA-2006 19-MCA-2006 31-MCA-2006

98
16-MCA-2006 19-MCA-2006 31-MCA-2006

98
16-MCA-2006 19-MCA-2006 31-MCA-2006

98
16-MCA-2006 19-MCA-2006 31-MCA-2006

98
16-MCA-2006 19-MCA-2006 31-MCA-2006

98
16-MCA-2006 19-MCA-2006 31-MCA-2006

98
16-MCA-2006 19-MCA-2006 31-MCA-2006

98
16-MCA-2006 19-MCA-2006 31-MCA-2006

98
16-MCA-2006 19-MCA-2006 31-MCA-2006

98
16-MCA-2006 19-MCA-2006 31-MCA-2006

98
16-MCA-2006 19-MCA-2006 31-MCA-2006

98
16-MCA-2006 19-MCA-2006 31-MCA-2006

98
16-MCA-2006 19-MCA-2006 31-MCA-2006

98
16-MCA-2006 19-MCA-2006 31-MCA-2006

98
16-MCA-2006 19-MCA-2006 31-MCA-2006

98
16-MCA-2006 19-MCA-2006 31-MCA-2006

98
16-MCA-2006 19-MCA-2006 31-MCA-2006

98
16-MCA-2006 19-MCA-2006 31-MCA-2006

98
16-MCA-2006 19-MCA-2006 31-MCA-2006

98
16-MCA-2006 19-MCA-2006 31-MCA-2006

98
16-MCA-2006 19-MCA-2006 31-MCA-2006

98
16-MCA-2006 19-MCA-2006 31-MCA-2006

98
16-MCA-2006 19-MCA-2006 31-MCA-2006

98
16-MCA-2006 19-MCA-2006 31-MCA-2006

98
16-MCA-2006 19-MCA-2006 31-MCA-2006

98
Future Enhancements
 Payment of Bills via online credit cards.
 To associate our Lab with Hospital.
 Online Sale/Purchase.
 Online patient registration
16-MCA-2006 19-MCA-2006 31-MCA-2006

98
Conclusion
Modern Medical Lab is computerized medical lab where the patient of all the age groups can go under
examination under the specialized doctors using the modern technologies. Supports registration of
patient, report generation, inventory management. Web-based interface for online test details, maintains
employee records, get appointment
The system validates the data fed into the system at earlier stages. Moreover, The system is able to
perform correctly provided the input is correct. It is observed that data fed into the computer is 100%
validated and no future validation checks are required. If there is any error in the input, the system
indicates the error to the user. So, the data entry time is very much reduced. Thus the system can be very
effective for a longer period of time.
16-MCA-2006 19-MCA-2006 31-MCA-2006

98
Bibliography
 ASP.NET on the Edge
Author: Rick Leinecker.
 Programming Microsoft Visual C#.Net
(Microsoft Press)
Author: Francesco Balena.
 Introducing .NET
WROX Publications.
16-MCA-2006 19-MCA-2006 31-MCA-2006

98
GLOSSARY
Analysis Breaking a problem into successively manageable parts for individual
study.
Attribute A data item that characterizes an object.
Database A store of integrated data capable of being directly addressed for multiple
users; it is organized so that various files can be accessed through a single
reference based on the relationship among records in the file rather than
the physical location.
DBMS The software that determines how data must be structured to produce the
user’s view; and maintain and update the system.
Data flow Movement of data in a system from a point of origin to a specific
destinations- indicated by a line and arrow.
Data security Protection of data from loss, disclosure, modification or destruction.
Data structure A logically related set of data that can be decomposed into lower level
data elements; a group of data elements handled as a unit.
Design Process of developing the technical and operational specifications of a
candidate system for implementation.
Feasibility Study A procedure that identifies, describes and evaluate candidate systems and
select the best system for implementation.
File Collection of related records organized for a particular purpose also called a dataset.
16-MCA-2006 19-MCA-2006 31-MCA-2006

98
Flow Chart A graphic picture of the logical steps and sequence involved in a
procedure or a program.
Form A physical carrier of data of information.
Gantt Chart A static system model used for scheduling; portrays output performance
against time.
Implementation In system development – a phase that focuses on user training, site
preparation and file conversion for installing a candidate system.
Maintenance Restoring to its original condition.
Normalization A process of replacing a given file with its logical equivalent; the object is
to derive simple files with no redundant elements.
Operating System In database – machine based software that facilitates the availability of
information or reports through the DBMS.
Password Identity authenticator a key that allow access to a program system or
procedure.
Source Code A Procedure or format that allow enhancements on a software package.
System A regular or orderly arrangements of components or parts in a connected
and interrelated series or whole; a group of components necessary to some
operation.
System Design Detailed concentration on the technical and other specifications that will
make the new system operational.
SDLC (System Development Life Cycle) A structured sequence of phases for implementing an
information system.
16-MCA-2006 19-MCA-2006 31-MCA-2006

98
System Testing Testing the whole system by the user after major programs and
subsystems have been tested.
Unit Testing Testing changes made in an existing or new programs.
Websites
16-MCA-2006 19-MCA-2006 31-MCA-2006

98
 http://www.vbnetdesign.com
 http://www.microsoft.com/vb.net
 http://www.webindia123.com/career/options/medlab/intro.htm
 http://en.wikipedia.org/wiki/medicallaboratory
16-MCA-2006 19-MCA-2006 31-MCA-2006

98
16-MCA-2006 19-MCA-2006 31-MCA-2006

98

A Project Reort

Uploaded by

Document Information

Original Description:

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

A Project Reort

Uploaded by

Copyright:

Available Formats

Medical Lab Patient Billing and Inventory Management System [ASP.

NET, C# & SQL-Server 2005]

"Together we create the Enterprises of Tomorrow"

"To provide world-class Information Technology solutions and services"

16-MCA-2006 19-MCA-2006 31-MCA-2006

as system integration, networking consultancy and a wide range of support services.

imaging and communication products.

16-MCA-2006 19-MCA-2006 31-MCA-2006

considerable dominance in verticals like finance, government, education and research.

Microsoft, Oracle, Cisco, Redhat.

16-MCA-2006 19-MCA-2006 31-MCA-2006

human effort and creativity.

examination under the specialized doctors using the modern technologies.

Patient Tests are best diagnosis of the patients’ health.

Aim of the Project

16-MCA-2006 19-MCA-2006 31-MCA-2006

working of Medical Labs and to maintain Test Record.

 It also maintains the required information of the employees in the Lab.

 To act System as a Source of information for Laboratory as well as for patients.

 To reduce manual work as much as possible.

 To provide information of registered patients without loss of time.

Scope of the Project

16-MCA-2006 19-MCA-2006 31-MCA-2006

doctors are stored manually in the form of Files and registers.

◦ Involves time constraint.

some transaction takes place is valid and correct.

o Provide Web based easy to use interface to the users.

in some other useful works.

16-MCA-2006 19-MCA-2006 31-MCA-2006

can be assigned to authorized users by the super user.

 ACCESS CONTROL (Who has the right to access the software)

 AUTHORISATION (Defining rights of an user)

 AUTHENTICATION (Checking who the user is)

 DATA INTEGRITY (Protection of data from modification and deletion)

 DATA SECURITY (Maintain confidentiality of data)

 PASSWORD INTEGRITY (Encryption of passwords)

of the following reason:

Few Other Problems

Patient reports cannot be stored forever.

Visitor Requests, Appointments and Feedback

16-MCA-2006 19-MCA-2006 31-MCA-2006

Patient Billing and Test Report Generation

Role and Responsibility

It is the responsibility of the members of the team presented in the paragraphs.

Project Manager (PM)

Project objectives especially those pertaining to quality engineering.

• Supervision for project.

• Ensuring that Project schedules are met.

• Monitoring man power and machine resources.

• Planning for and responding to any contingencies.

• Monitoring quality of program system test.

16-MCA-2006 19-MCA-2006 31-MCA-2006

responsibilities would include:

• Coordination of development work.

• Interface between modules.

Module Leader/Team Members/Programmers

These professionals would provide support in the areas of:-

• Monitoring and Project Review

• Assistance in system Testing.

16-MCA-2006 19-MCA-2006 31-MCA-2006

Guide), Project Leader, Software professional and Quality Coordinator.

TEAM LEADER (External Project Guide)

Rajinder Kr. Chitoria