1.
DOCKIKKO
MODULE : DOCTOR
P V NEERAJ SONA
C0GMCA2208

2.
INTRODUCTION
• Introducing our new app for doctors, designed to make
managing patient information and appointments as easy as
possible.
• With user-friendly interface, you can access patient records,
prescribe medications, schedule appointments, and more.

3.
EXISTING SYSTEM
• Yes, there are several existing systems for managing patient
information and appointments for doctors.
• Some popular examples of practice management systems
include AdvancedMD and Kareo.

4.
PROBLEMS ON EXISTING SYSTEM
• Complexity
• High cost
• Data entry errors

5.
PROPOSED SYSTEM
• To over come all the limitations in existing system
• The proposed system for managing patient information and
appointments for doctors would aim to address some of the
disadvantages of existing systems, such as high cost,
complexity, and limited interoperability
• Affordable pricing
• User-friendly interface
• Advanced security

6.
DOCTOR
• Appointment
• Add Doctor
• Delete Doctor
• Doctor Activity
• Patient Details
• Update Doctor
• Search Doctor
• View Doctor

7.
ARCHITECTURE
• Managing patient information and appointments for doctors
would likely be based on a client-server model
• This would involve a central server that stores and manages all
patient information and appointments, and a client application
that allows doctors and other staff members to access and
interact with this information

8.
• The client application could be a web-based application or a
mobile app, depending on the preference of the practice
• while the mobile app would allow them to access the
information from their smartphones or tablets.
• The server would use a relational database management
system (RDBMS) to store and manage the data.

9.
• The system would also include an Application Programming
Interface (API) that allows the system to communicate with other
systems, such as lab systems or other Google map
• In terms of security, the system would use a combination of
technologies such as secure socket layer (SSL)
• For communication encryption and access control mechanisms
like role-based access control (RBAC) to ensure that patient
information is protected from unauthorized access.

10.
MODEL
• System follows INCREMENTAL MODEL because initially software
requirements are reasonably well defined but the overall scope of
development effort is a purely linear process. There may be other
requirements of the user which will be known later. So, those
requirements can the implemented and delivered in the following
next increments.

11.
Screenshots

12.
DFD LEVEL 0