Project Introduction

This is a Hospital Management System developed using-

It's a client based project meaning the software is being used this very moment while you are reading this article. I will try to cover all the sections of this project and discuss the modular approach taken while development.

Institution

The institution using this software is Mainamati Cantonment General Hospital.

Location:
Tipara Bazar, Mainamati.
Cumilla cantonment.
Cumilla.

Modular Approach

This project was divided in 5 different modules. I've descriptive videos explaining the modules and giving a project over view within the module scope.

• Module 01
• Module 02
• Module 03
• Module 04
• Module 05

Each module dealt with one or more user types.

User Authentication

User authentication was a big challenge in this project since I had to authenticate different types of accounts using the same login page. We also had to manage the user access as well thru the whole software.

This was much easier because of the Laravel framework and it's built in middleware and routing settings.

Types of users

There are 6 types of users in our software.

• Receptionist
• Doctor
• OT Operator
• Nurse
• Accountant
• Admin

They all have unique ID templates that separates them while authentication.

Receptionist End Overview

Reception is one of the function heavy portions of the software.

Services

There are 6 types of services that can be provided from the receptionist end.

• Outdoor patient registration.
• Patient admission.
• Pathology section.
• Dental services.
• Physiotherapy.
• Emergency.

Each of these services has there own interface, that I've covered within the video overviews of Module 01, Module 02 and Module 03.

Invoice Generator

This portion also has a very powerful invoice generator, which not only generates but also filters invoices across all the different types of services.

Doctor End Overview

Doctor end is more on the light side when compared with the other ends functionality wish.

Actions

• Profile setup.
• Patient list browsing.
• Patient confirmation.
• Schedule editor.
• Operation schedule browsing.
• Log browsing.

I've covered all the features in the video overview of Module 01.

OT End Overview

OT end has a number of functionality that is mostly connected with other ends. While being comparably light it still has an effective number of functions.

Actions

• Schedule creation and management.
• Data entry on operated patients.
• Invoice generation.

I've covered all the features in the video overview of Module 02.

Nurse End Overview

Nurse end will deal with the admitted patients from reception end. This has a moderate amount of functions and does a lot of patent data tracking.

Actions

• Patient list browsing & filtering.
• Invigilator tracking.
• Providing other services.
• Tracking provided services.
• Generating virtual patient chart.

I've covered all the features in the video overview of Module 02.

Accounts End Overview

Accounts is the second most feature heavy portion after admin. Everything related to transactions is tracked by this portion.

Actions

• Profile setup.
• Important variable setup.
• Income tracking.
• Receptionist cash check-in.
• Salary payment.
• Creditor management.
• Admitted patient list browsing.
• Issuing patient release.
• Invoice generation.
• Ambulance expense tracking.
• Other expenses tracking.
• Log browsing & filtering.

I've covered all the features in the video overview of Module 04.

Admin End Overview

This has authority over the whole system. So It is packed with functionality.

Actions

• Profile setup.
• Dashboard browsing.
• Built in personal & global activity log.
• Income summarization.
• Logs filtering.
• Employee status control.
• Employee add, edit & delete privileges.
• Bed add, edit & delete privileges.
• Bed status preview.
• Pathology services add, edit & delete privileges.
• Dental services add, edit & delete privileges.
• Other services add, edit & delete privileges.

I've covered the entirety of this end in the video overview of Module 05.

Requirement

Now let's discuss the minimal hardware & software requirements to run this software.

Hardware

End	Processor	RAM	HDD
Client	Intel Core i3 (4th gen)	2 GB	80 GB
Server	AMD Ryzen 7	32 GB	120 GB

Software

Topics	Specifications
OS	Windows 7/8/8.1/10/11
Front End	HTML, CSS, JavaScript
Back End	PHP 8.0.7
Framework	LARAVEL 8.49.2
Database	MySQL
Tools	XAMPP

Limitations

There were some conditions given between development.

• Server will not be connected to internet.
• LAN connections will be maintained between server and client devices for data transfer purposes.

Based on these conditions some problems were introduced

• Any kind of frontend framework were crossed of the chart while development.
• All assets were self build in the software.
• A built in framework was designed and developed, later used in the front end development.

Issues

Currently no known Issues.