1) The document describes a web application created to manage patient records for an orthopedic surgery department more efficiently. 2) It addresses issues with the previous paper-based system like lost time finding records and limited storage. 3) The new application uses a MVC architecture with a MySQL database backend and features like online access and automated notifications to improve patient follow-up.

1. Realized by:
BENMBARKA Mohammed.
ERGUIBI Mohamed Said.
HACHMI Saad.
Conception and implementation of a web application for
Managing Patients for the Orthopaedic Surgery and
Traumatology A.
IT Engineering and Networks.
Academic year 2022/2023
English

2. SUMMARY
I II
IV V
INTRODUCTION PROBLEMATIC
TECHNOLOGIES CONCLUSION
VI
DEMO
III
ARCHITECTURE

3. Introduction

4. Problematic

5. 5
- Loss of time in the old method of managing patients.
- Sometimes doctors can't find patients records.
- Data storage problems because they use a single fixed computer which contains the old
application and has a capacity of only 500 GB.
- It does not have an online platform that allows Traumato service doctors access to
patient records.
- The absence of follow-up of the state of the patient because there are patients who are
obliged to do a control after 6 weeks or 12 weeks of the operation, but because of the
absence of the notification system for the doctors, the patients exceed the time of the
control, is that will produce side effects which oblige another operation for the patient.

6. Architecture

7. Architecture
• MVC - Model-View-Controller - is a design pattern
for the architecture of web applications.
• It is a widely adopted pattern, across many
languages and implementation frameworks, whose
purpose is to achieve a clean separation between
three components of most any web application.
Définition

8. MVC

9. Model (Définition)
The Model represents the structure of the data in the
application, as well as application-specific operations
on those data.

10. Architecture
• Responsible for managing the data.
• Stores and retrieves entities used by an application,
usually from a database but can also include
invocations of external web services or APIs.
• Contains the logic implemented by the application
(business logic).
Model (Utility)

11. View (Définition)
The View renders the contents of a model. It
specifies exactly how the model data should be
presented.

12. View (Utility)
Responsible to display the data provided by the
model in a specific format

13. Controller
(Définition)
The Controller translates inputs into application
function calls on the model, and selects the
appropriate View based on user preferences and Model
state.

14. Controller (Utility)
• Handles the model and view layers to work together.
• Receives a request from the client, invokes the model
to perform the requested operations and sends the
data to the view.

15. Technologies

16. JQuery
02
PHP
01
Javascript
05
Html5
04
Mysql
03
Css3
06

17. Demo

18. Conclusion

19. Thank you for your attention !