GUJARAT TECHNOLOGICAL UNIVERSITY

Darshan Institute of
Engineering and Technology,
Rajkot
(Affiliated with GTU)

A Mini Project Report on

“Doctor Dictionary”

Under the subject

Summer Internship (3170001)

B. E. IV, Semester - VII

Department of Computer Engineering

Submitted By
Saradva Meet Shankarbhai 200540107007

Academic Year
(2023-24)

Internal Guide Head of the Department

Dr. Gopi Sanghani Dr. Gopi Sanghani
Professor & Head, Professor & Head,
CE Department, DIET CE Department, DIET
 Darshan Institute of
Engineering and Technology,
Rajkot
(Affiliated with GTU)

DECLARATION

We hereby declare that the Report, submitted along with the Summer
Internship (3170001) for entitled “Doctor Dictionary” submitted in partial
fulfilment for the degree of Bachelor of Engineering in Computer Department to
Gujarat Technological University, Ahmadabad, is a record of the work carried out
by Darshan Institute of Engineering and Technology, Rajkot under the
supervision of (Dr. Gopi Sanghani) and that no part of any of report has been
directly copied from any students’ reports, without providing due reference.

Name of the student

Saradva Meet Shankarbhai
 Darshan Institute of
Engineering and Technology,
Rajkot
(Affiliated with GTU)

DEPARTMENT OF COMPUTER ENGINEERING

CERTIFICATE

This is to certify that the mini project on Doctor Dictionary has been
satisfactorily carried by Saradva Meet Shankarbhai (200540107007) under my
guidance in the fulfillment of the course Summer Internship (3170001) work
during the academic year 2023-24.

Internal Guide Head of the Department

Dr. Gopi Sanghani Dr. Gopi Sanghani
Professor & Head., Professor & Head,
CE Department, DIET CE Department, DIET
Acknowledgement

I wish to express my sincere gratitude to my project guide Prof. Dr. Gopi Sanghani
and all the faculty members for helping me through my project by giving me the
necessary suggestions and advices along with their valuable co- ordination in
completing this work.

I also thank my parents, friends and all the members of the family for their precious
support and encouragement which they had provided in completion of my work. In
addition to that, I would also like to mention the college personals who gave me the
permission to use and experience the valuable resources required for the project from
the college premises.

Thus, in conclusion to the above said, I once again thank the faculties and members
of Darshan Institute of Engineering & Technology for their valuable support in
completion of the project.

Thank You
Saradva Meet Shankarbhai
ABSTRACT

A doctor information list is a database of information about doctors. It can include information such
as the doctor's name, specialty, education, experience, and location. It can also include information
about the doctor's licensing and certification status, as well as patient reviews. Doctor information
lists can be used for a variety of purposes, such as finding a new doctor, researching a doctor's
qualifications, or comparing different doctors. They can also be used by insurance companies to
verify that a doctor is in their network and by hospitals to track their patient population. A doctor
information list is a directory of doctors that contains information about their specialty, location,
and contact information. This type of list can be a valuable resource for patients who are looking
for a new doctor or who need to find a doctor in a new area. There are a number of different ways
to find a doctor information list. One option is to search online for "doctor directory." Another
option is to contact your local medical society or health insurance company. They may be able to
provide you with a list of doctors in your area who are in your network.

Page | i
Table of Contents
Table of Contents.......................................................................................................................... II
List of Figures…………………………………………………………………………………… III
List of Tables…………………………………………………………………………………….. III
1. Introduction.............................................................................................................................. 1
1.1 Purpose...................................................................................................................... ....................... 1
1.2 Document Conventions............................................................................... ..................................... 1
1.3 Intended Audience and Reading Suggestions.................................................................................. 1
1.4 Project Scope................................................................................................................................... 1
2. Overall Description.................................................................................................................. 2
2.1 Product perspective.......................................................................................................................... 2
2.2 Product features.............................................................................................................................. 2
2.3 User Classes and Characteristics...................................................................................................... 3
2.4 Operating environment.................................................................................................................... 4
2.5 Design and Implementation Constraints.......................................................................................... 4
2.6 User documentation........................................................................................................................ 4
2.7 Assumptions and Dependencies....................................................................................................... 4
3. System Features....................................................................................................................... 5
3.1 Functional requirement................................................................................................................... 5
3.2 Use case Diagram............................................................................................................................. 6
4. External Interface Requirements........................................................................................... 7
4.1 User interfaces................................................................................................................................. 7
4.2 Hardware interfaces........................................................................................................................ 9
4.3 Software interfaces.......................................................................................................................... 9
4.4 Communications interfaces.............................................................................................................. 9
5. Other Non-functional Requirements....................................................................................... 10
Security…………............................................................................................................................. 10
Availability....................................................................................................................................... 10
Safety requirements.......................................................................................................................... 10
Security requirements................................................................................................................. ...... 10
Software quality attributes................................................................................................................ 10
Hardware constraints........................................................................................................................ 10
Software constraints......................................................................................................................... 10
Alert constraints…........................................................................................................... .................. 10
6. Implementation……………………………………………………………………………… 11

Appendices......................................................................................................................................
References………………………………………………………………………………………..

Page | ii
 List of Figures

Sr. Figure Name Page

2.2 Context diagram of Doctor Dictionary 3
3.2 Usage diagram of Doctor Dictionary 6
5.1, Screenshots of implementations in Doctor Dictionary 11
5.2
5.3, Screenshots of implementations in Doctor Dictionary 12
5.4
5.5, Screenshots of implementations in Doctor Dictionary 13
5.6
5.7, Screenshots of implementations in Doctor Dictionary 14
5.8
6A Activity Diagram of Doctor Dictionary 15
6B E-R Diagram of Doctor Dictionary 16
6C Class Diagram of Doctor Dictionary 17
6D Sequence diagram for Find of Doctor 18
-1
6D (Fig.5D-2 Sequence diagram for Patient ) 18
-2
6E- State diagram for Patient 19
1
6E- State diagram for Doctor 19
2
6F Dataflow Diagram of Doctor Dictionary 20

List of Tables

Sr. Table Name Page

2.4 Operating Environment 4

Page | iii
 Doctor Dictionary

1. Introduction
1.1 Purpose
The purpose of doctor dictionary application is a mobile or web-based application that provides
doctors with quick and easy access to medical definitions, abbreviations, and other resources. It
can be used to look up terms on the fly during patient encounters. By being able to provide their
patients with accurate and up-to-date information, doctors can improve patient satisfaction and
build trust with their patients. This project describes the hardware and software interface
requirements using ER diagrams and UML diagrams.

1.2 Document Conventions

 Context: A broad level diagram of the project showing a basic overview.

 Use Case: summarizes some of the relationships between Cases, user, and systems.
 UML: Unified Modeling Language
 DD: Doctor Dictionary
 Cataloguing: is a module for entries that are related to a particular disease or condition.
 Circulation: is a module for issue and return material for patients.

1.3 Intended Audience

The intended audiences for this document are:

  Software Project Managers

  Software Engineers
  Patients and consumers
 Doctors and other healthcare professionals

1.4 Project Scope

This project is basically a comprehensive database of medical definitions, including
abbreviations, acronyms, and eponyms, availability of books etc , The ability to share terms with
other doctors or patients , Disease information, including symptoms, causes, and treatment
options , Medical images, such as images of radiology scans, lab tests, and other medical
procedures, The application allows users to search for doctors by name, specialty, location, and
other criteria.

Page | 1
 Doctor Dictionary

2. Overall Description
2.1 Product Perspective
The Doctor Dictionary application includes information about as many doctors as possible,
including doctors from a variety of specialties and locations contain accurate and up-to-date
information about doctors. Users should be able to quickly and easily find the information they
need, such as a doctor's contact information, specialty, and location.

2.2 Product Features

There are four different users who will be using this product:

 Doctors and other healthcare professionals can use the application to Look up
information about doctors, such as their specialty, location, contact information, and
 education and training.
  Member who will be accessing the doctor dictionary list.
  Patients and consumers can read patient reviews of doctors.
 Patients and consumers can get information about a doctor's education and training.

The features that are available to the Patients are:
 View detailed information about a doctor, including their education, training, experience,
 and patient reviews.
 View a list of doctors that match the search criteria, including the doctor's name,
 specialty, location, contact information, and other relevant information.
  Receive notifications about new doctors and medical news.
  The ability to book appointments with doctors directly through the application.
 A patient can use the application to save their favourite doctors to a list for future
reference.
 The ability to receive notifications about new doctors and medical news.


The features that are available to the Doctors are:

  A doctor can use the search feature to find a specialist that they need to refer a patient to..
 A doctor can use the view detailed information feature to learn more about a new doctor
 who is joining their practice.
 A doctor can use the regularly updated with new information and features feature to stay
 up-to-date on the latest medical knowledge and trends.
 A doctor can use the integrate with other medical software feature to easily share patient
information with other doctors and healthcare professionals.

Page | 2
 Doctor Dictionary

Cataloguing
You can create a catalogue of your Diseases and conditions, Specialists and all similar
collections using this module.
Circulation
Circulation module deals with doctor to patient’s interactions. It has a diseases specialization
for all patients goes for particular diseases and solve their problem to relatable and their
choice according to the doctor rating and education performance and all specific criteria.

(Fig 2.2 context diagram of Doctor Dictionary)

2.3 User Classes and Characteristics

There are various kinds of user visits the product for different reason.

 Doctors: A doctor can use the search feature to find a specialist that they need to refer a
 patient to and also need to communicate with patients in a clear and concise way.
 Patients: View a list of doctors that match the search criteria, including the doctor's
 name, specialty, location, contact information, and other relevant information.
 Insurance companies: To check the patient's giving correct information about insurance
bill payment claim for documentation verification.

Page | 3
 Doctor Dictionary

2.4 Operating Environment

The doctor dictionary application list can be used on desktop computers running Windows,
macOS, or Linux. Not requirement to use this product would be the internet connection always
available.

User Particulars Client System Server System

Doctors Operating System Windows Windows Server
And Processor Dual core (Minimum) Pentium 4.0 GHz or
Patients higher
(Windows Hard disk 123 GB (Minimum) 1 GB
Application ) RAM 512 MB (Minimum) 80 GB
Operating System Android 4.0 and Higher
Patients Processor Octa Core (Minimum)
(Mobile App) Enteral Memory 512 MB (Minimum)
RAM 512 MB (Minimum)

2.5 Design and Implementation Constraints

Doctor dictionary application should be comprehensive enough to meet the needs of a wide
range of users, including doctors, patients, and medical students. This means that the application
should include a wide range of doctors or patients , Disease information, including symptoms,
causes, and treatment options , Medical images.

2.6 User Documentation

The product will include user manual. The user manual will include product overview, complete
configuration of the used software, technical details, backup procedure and contact information
which will include email address. There will be no online help for the product at this moment.

2.7 Assumptions and Dependencies

  The application will be used on a variety of devices and operating systems.

  Allow users to save their favourite doctors to a list for future reference.
 The search bar should be prominently displayed on the home screen of the application.
 This will allow users to quickly and easily find the doctors they are looking for.
 Avoid using technical jargon or acronyms in the UI. If you do need to use technical
terms, be sure to define them clearly.

Page | 4
 Doctor Dictionary

3. System Feature
3.1 Function Requirement

Doctors and other healthcare professionals

 Look up information about doctors, such as their specialty, location, contact

information, and education and training.
 Find doctors who are experts in a particular disease or condition.
 The application should allow users to search for doctors by name, specialty, location,
and other criteria.
 The application should display a list of doctors that match the search criteria,
including the doctor's name, specialty, location, contact information, and other
relevant information.
 The application should allow users to view detailed information about a doctor,
including their education, training, experience, and patient reviews.
 The application should be updated regularly with new information and features.

Patients and consumers

 Find and research doctors in their area.

 Learn more about different medical specialties.
 Read patient reviews of doctors.
 Get information about a doctor's education and training.
 Find doctors who are experts in a particular disease or condition.
 A doctor could use the application to look up the contact information of a specialist
that they need to refer a patient to.
 A nurse could use the application to learn more about a new doctor who is joining
their practice.
 A patient could use the application to find a doctor who is in their insurance network
and who is accepting new patients.
 The ability to book appointments with doctors directly through the application.
 The ability to read and write patient reviews.
 The ability to receive notifications about new doctors and medical news.
 The ability to create and share personalized medical profiles with doctors and other
healthcare professionals.

Page | 5
 Doctor Dictionary

3.2 Usage Diagram

(fig. Use case diagram of Doctor Dictionary)

Page | 6
 Doctor Dictionary

4. External Interface Requirements

4.1 User Interface

 Doctor Details


 Hospital Details

Page | 7
 Doctor Dictionary

 Specialization

 Doctor Availability Time

 Doctor Availability Day

Page | 8
 Doctor Dictionary

4.2 Hardware Interface

 The doctor information application may be installed on desktop computers, laptops, or
tablets. The doctor information application may require networking equipment, such as
routers and switches, to connect to the internet or to other systems.


4.3 Software Interface

Server

  Operating System: Windows

 Processor: Pentium 4.0 GHz or higher
 RAM: 1GB Mb or more
 Hard Drive: 80 GB or more
Client

  Operating System: Windows and Android and IOS

  Processor: Pentium III or 2.0 GHz or higher or Octa.
 RAM: 512 Mb or more
Database: SQlLiteStudio
Development Tools: Android Studio, Visual Studio

4.4 Communication Interface

Communication between server and application system need the internet connection into system.
Because all the data will be available in server database. Using the web services fetch the data
from the server.

Page | 9
 Doctor Dictionary

5. Non Functional Requirement

Security
The system can be secure to avoid unwanted users to asses this system without granted
permission.

Availability
It can also site that can login in chrome access and User can install application from Apple
App Store and Google Play Store and look for regular updates give ratting and feedback.
When application is made to start up with company logo it shouldn’t take more than 5 second
to load initial screen. Also, it should be made sure that app will not hindrance to the user
Input.
Safety requirements
The database may get crashed at any certain time due to virus or operating system failure.
Therefore, it is required to take the database backup.
Security requirements
We are going to develop a secured database for the university .there are different categories
of users namely teaching staff, administrator, library staff ,students etc., depending upon the
category of user the access rights are decided. It means if the user is an administrator then he
can be able to modify the data, delete, append etc., all other users other than library staff only
have the rights to retrieve the information about database.
Software quality attributes
The quality of the database is maintained in such a way so that it can be very user friendly to
all the users of the database.
Hardware constraints
The system requires a database in order to store persistent data. The database should have
backup capabilities.
Software constraints
The development of the system will be constrained by the availability of required software
such as database and development tools. The availability of these tools will be governed by
Alert constraints
Sometime user miss the submit book and article on return data, so system will be give the
return book alert message on member mobile before one day of return date. And also provide
alert for upcoming new books and article.

Page | 10
 Doctor Dictionary

6. Implementation

(Fig 5.1 and 5.2 contains the disease list and it is a Home screen of the doctor dictionary)

Page | 11
 Doctor Dictionary

(Fig 5.3 and 5.4 contains the Doctor details and navigate for check Available timing & location)

Page | 12
 Doctor Dictionary

(Fig 5.5 and 5.6 contains the doctor list of specific disease or specialist doctor list )

Page | 13
 Doctor Dictionary

(Fig 5.7 and 5.8 showing the doctor’s detail of Available timing and location )

Page | 14
 Doctor Dictionary

Appendices
A) Activity Diagram

(Fig.6A Activity Diagram of Doctor Dictionary )

Page | 15
 Doctor Dictionary

B) E-R Diagram

(Fig.6B E-R Diagram of Doctor Dictionary )

Page | 16
 Doctor Dictionary

C) Class Diagram

(Fig.6C Class Diagram of Doctor Dictionary )

Page | 17
 Doctor Dictionary

D) Sequence Diagram
 Sequence diagram for Find Doctor

(Fig.6D-1 Sequence diagram for Find of Doctor )

 Sequence diagram for Patient

(Fig.6D-2 Sequence diagram for Patient )

Page | 18
 Doctor Dictionary

E) State Diagram
 State diagram of Patient

(Fig.6E-1 State diagram for Patient )

 State diagram of Doctors

(Fig.6E-2 State diagram for Doctors )

Page | 19
 Doctor Dictionary

F) Dataflow Diagram

(Fig.6F Dataflow Diagram of Doctor Dictionary )

Page | 20
 Doctor Dictionary

References

 https://medical-dictionary.thefreedictionary.com/
 https://medlineplus.gov/encyclopedia.html
 https://www.webmd.com/
 https://www.mayoclinic.org/
 https://www.cdc.gov/
 https://www.clevelandclinic.org/
 https://www.uclahealth.org/
 https://www.hopkinsmedicine.org/

Page | 21