PROJECT REPORT

ON
“REPORT COLLECTION OF DATA FROM HOSPITAL”

SUBMITTED IN PARTIAL FULFILLMENT OF THE REQUIREMENTS FOR

THE AWARD OF DIPLOMA IN COMPUTER ENGINEERING

SUBMITTED TO MAHARASHTRA STATE BOARD OF

TECHNICAL EDUCATION,MUMBAI

SUBMITTED BY

Sr No. Name of Student(s) Enrollment no.

1. MAYANK THOOL 23313400176
2. DIVYA SHUKLA 23313400183
3. PRACHI GOHATE 23313400185
4. SHARAN ASEKAR 23313400187
5. PRANALI KATRE 23313400189

GUIDED BY : Miss. Prerna Kadu

1
 J D COLLEGE OF ENGINEERING & MANAGEMENT
(1201)

CERTIFICATE

THIS IS TO CERTIFY THAT THE PROJECT REPORT ENTITLED “REPORT COLLECTION OF DATA
FROM HOSPITAL”WAS SUCCESSFULLY COMPLETED BY STUDENTS OF FIFTH SEMESTER
DIPLOMA IN COMPUTER ENGINEERING.
r

MAYANK THOOL 23313400176

DIVYA SHUKLA 23313400183
PRACHI GOHATE 23313400185
SHARAN ASEKAR 23313400187
PRANALI KATRE 23313400189

IN PARTIAL FULFILLMENT OF THE REQUIRMENTS FOR THE AWARD OF THE DIPLOMA IN

COMPUTER ENGINEERING AND SUBMITTED TO THE DEPARTMENT OF JD COLLEGE OF
ENGINEERING AND MANAGEMENT,NAGPUR WORK CARRIED OUT DURING A PERIOD OF
ACADMEIC YEAR 2024-2025 AS PER CURRICULLUM.

NAME OF GUIDE NAME OF HOD

(MISS.PRERNA KADU) (MRS.NIKITA KANPHADE)

2
 TEACHER EVALUATION SHEET FOR MICRO PROJECT

COURSE TITLE AND CODE:EST (ENVIRONMENTAL STUDIES)(22447)

TITLE OF THE PROJECT: REPORT COLLECTION OF DATA FROM HOSPITAL
GROUP NO:06
Co’s Addressed by The Microproject:

CO4 Collecting Data From Hospital

MARKS:

ROLL NAME OF MARKS MARKS TOTAL REMARK

NO. STUDENTS FOR BASED ON MARKS
GROUP VIVA(04) (10)
WORK(06)
45) MAYANK
THOOL
49) DIVYA SHUKLA
34) PRACHI GOHATE
35) SHARAN ASEKAR
37) PRANALI KATRE

NAME AND SIGNATURE OF FACULTY: MISS.PRERNA KADU

SIGN:_______________

3
 INDEX

Sr. CONTENTS PG NO.

No.
1. ABSTRACTS 5
2. INTRODUCTIONS 6
3. MODULES 7
4. FLOWCHART 11
5. ER DIAGRAM 12
6. DATA FLOW DIAGRAM 13
7. ADVANTAGES 14
8. REQUIREMENTS 15
9. CONCLUSION 16
10. REFERENCES 17

4
 ABSTRACT

Our Project REPORT COLLECTION OF DATA FROM HOSPITAL Includes Registration Of

Patients, Storing Their Details Into The System, And Also Booking Their Appointments With

Doctors.

Our Software Has The Facility To Give A Unique Id For Every Patient And Stores The Details Of

Every Patient And The Staff Automatically. User Can Search Availability Of A Doctor And The

Details Of A Patient Using The Id. The Hospital Management System Can Be Entered Using A

Username And Password. It Is Accessible Either By An Administrator Or Receptionist. Only They

Can Add Data Into The Database. The Data Can Be Retrieved Easily. The Interface Is Very User-

Friendly. The Data Are Well Protected For Personal Use And Makes The Data Processing Very

Fast.

5
 INTRODUCTION

In this busy world we don’t have the time to wait in infamously long hospital queues. The

problem is, queuing at hospital is often managed manually by administrative staff, then take a

token there and then wait for our turn then ask for the doctor and the most frustrating thing - we

went there by traveling a long distance and then we come to know the doctor is on leave or the

doctor can’t take appointments. This will help us overcome all these problems because now

patients can book their appointments at home, they can check whether the doctor they want to meet

is available or not. Doctors can also confirm or decline appointments, this help bothpatient and the

doctor because if the doctor declines’ appointment then patient will know this in advance and

patient will visit hospital only when the doctor confirms’ the appointment this will save time and

money of the patient.

6
 MODULES

 Number of external inputs (EIs) - Each external input originates from a user
or is transmitted from another application and provides distinct application-
oriented data or control information. Inputs are often used to update internal
logical files (ILFs). Inputs should be distinguished from inquiries, which are
counted separately.

 Number of external outputs (EOs) - Each external output is derived data

within the application that provides information to the user. In this context
external output refers to reports, screens, error messages, etc. Individual data
items within a report are not counted separately.

 Number of external inquiries (EQs) - An external inquiry is defined as an

online input that results in the generation of some immediate software
response in the form of an online output (often retrieved from an ILF).

 Number of internal logical files (ILFs) - Each internal logical file is a

logical grouping of data that resides within the application’s boundary and is
maintained via external inputs.

 Number of external interface files (EIFs). - Each external interface file is a

logical grouping of data that resides external to the application but provides
information that may be of use to the application.

7
Screen EI EOs EQs ILFs EIF
No s s
1. Select - 1.Doctor’s Hospital -
Languag On Leave File
e 2.Visitors on
Website
2. - - - - -
3. 1. Username - - Hospital -
2. Password File
4. 1 .Name - - Hospital -
2 .Dob File
3. Gender
4 .Email
5. Blood
Group 6
.Mobile No
7 .Address
8 .CGHS / Private
9.Card Picture
5. - 1.Profile - HF -
6. 1. Department - - Hospital -
2 .Date File
3 .Time
4 .Doctor Name
7. 1.Appointment Hospital -
Status File
8. 1 .Card - - Hospital -
Holder Name File
2. Card number
3. Expire Date
4. CVC Number
9. 1.Registered - - Hospital -
Mobile No. File
2.Edit Appt.
Schedule
10. - - 1.Payment Hospital -
History File
11. - 1.Profile - HF -
8
12. 1.Doctor ID 1.Doctor Hospital -
Details File
13. - 1.Bill - Hospital -
File
14. 1. Username - - Hospital -
2. Password File
15. - 1. Profile Hospital -
File
16. - - 1.appt. Hospital -
Details File
17. 1. Treatment 1.Patient - Hospital -
Name Profile File
2 .Medicine
3 .Advice
4 .Remark
5.Patient ID
18. 1. Username - - Hospital -
2. Password File
19. 1.Payment - - Hospital -
Verify File
20. 1 Name - - Hospital -
2 Age File
3 Gender
4 Specialization
5 Experience
6 Language
7 Mobile No
8 Email Id
9 Schedule
21. 1.Doctor Id 1.Doctor - Hospital -
Profile File
22. 1.Select - 1.Records Hospital -
Monthly/Yearl File
y2.Select Year
3.Select Month

9
TOTAL EXTERNAL INUPUTS = 41
TOTAL EXTERNAL OUTPUTS = 7
TOTAL LOGICAL INTERNAL FILES = 1
TOTAL EXTERNAL INQUIRIES = 6

TOTAL EXTERNAL INTERFACE FILES = 0

10
FLOWCHART

11
ER DIAGRAM

12
Data Flow Diagram

13
 ADVANTAGES

 The system automates the manual procedure of managing hospital activities.

 Doctors can view their patients’ treatment records and details easily.

 It even generates an instant bill.

 The system is convenient and flexible to be used.

 It saves their time, efforts, money and resources.

14
 REQUIREMENTS

 Performance Requirements:

o Response time- The system will give responses within 1 second after

checking the patient information and other information.

o Capacity-The system must support 1000 people at a time

o User interface- User interface screen will response within 5 seconds

15
 CONCLUSION

Today, Almost No Model Can Estimate The Cost Of Software With High Degree Of
Accuracy. This State Of The Practice Is Created Because:

1. There Are A Large Number Of Interrelated Factors That Influence The Software
Development Process Of A Given Development Team And A Large Number Of
Project Attributes ,Such As Number Of User Screens, Volatility Of System
Requirements And The Use Of Reusable Software Components

2. The Development Environment Is Evolving Continously.

3. The Lack Of Measurement That Truely Reflects The Complexity Of A Software

System.To Produce A Better Estimate,We Must Improve Our Understanding Of
These Project Attributes And Their Casual Relationships,Model The Impact Of
Evolving Environment ,And Develop Effective Ways Of Measuring Software
Complexity.

16
 REFERENCES

1. Abdel-Hamid. T.. and Madnick, S. Impact of schedule estimation on software project

behavior. IEEE Softw. 3,4 (July 19861, 70-75.

2. Albrecht, A.J. Measuring application development productivity. In Proceedinns of fhe

IBM Applications Development Symposium, GUIDE/ SHARE (Goiterey, Calic,‘Oct.
14-17).

3. IBM, 1979,‘pp. 83-92. Albrecht. A.J.. and Gaffney. J., Jr. Software function, source lines
of code, and development effort prediction: A software science validation. IEEE Trans.
Softw. Eng. SE-g, 6 (Nov. 1963), 639-646. Behrens. CA. Measuring the productivity of
computer systems development activities with Function Points.

4. IEEE Trans. Softw. Eng. SE-g, 6 (Nov. 1963). 646-652. Boehm, B.W. Software
Engineering Economics. Prentice-Hall, Englewood Cliffs, N.J.. 1981. Brooks, F.P. The
Mythical Man-Month. Addison-Wesley, Reading. Mass.. 1975.

5. Call&m, H., and Colborne, S. A proposed method for estimating software cost from
requirements. J. Parmetrics 4,4 (Dec. 1984), 33-40.

6. Conte. S., Dunsmore, H.. and Shen, V. Software Engineering Metrics and Models.
Benjamin/Cummings, Menlo Park. Calif., 1986.

17