The specification of the Hospital Management System database is posted on this page. The database is a list of information that is uniformly placed in rows and columns in tables. The database table has a special name that describes its contents. The database, in turn, is further explained in-depth with all fields used for data types, limitations available, primary key, and foreign key.
The architecture of the database is used to handle broad knowledge bodies. In this database, we define the four tables available in the program that is used to store all information.
Data types and its description:
The fields in the database table have a category of data. Any of the forms of data used in the database table are explained below.
(a) Integer:-
One optional character (+ or-) followed by at least one digit (0-9). Leading and trailing blanks would be overlooked. There is no other character permitted.
(b) Varchar:-
It is used to store alphanumeric characters. In this data type, the maximum number of characters up to 8000 ranges can be set to 50 characters in size by default SQL server.
(c) Date/Time:
The data form Date/Time is used to represent data or time.
Patient Table:
| Fields | Data Type | Relationships |
| Pid | Varchar(5) | Primary Key |
| name | Varchar(20) | Not Null |
| age | int | Not Null |
| weight | int | Not Null |
| gender | Varchar(10) | Not null |
| address | Varchar(50) | Not Null |
| phoneno | int | Not Null |
| disease | Varchar(20) | Not Null |
| doctorid | Varchar(5) | Not Null |
Doctor Table:
| Fields | Data Type | Relationships |
| doctorid | Varchar(5) | Primary Key |
| doctorname | Varchar(15) | Not Null |
| dept | Varchar(15) | Not Null |
Lab Table:
| Fields | Data Type | Relationships |
| labno | Varchar(5) | Primary Key |
| pid | Varchar(5) | Not Null |
| weight | int | Not Null |
| doctorid | Varchar(5) | Foreign Key |
| date | Date/Time | Not Null |
| category | Varchar(15) | Not Null |
| patient_type | Varchar(15) | Not Null |
| amount | int | Not Null |
Inpatient Table:
| Fields | Data Type | Relationships |
| pid | Varchar(5) | Primary Key |
| room_no | Varchar(50) | Not Null |
| date_of_adm | Date/Time | Not Null |
| date_of_dis | Date/Time | Not Null |
| advance | int | Not Null |
| labno | Varchar(5) | Foreign Key |
Outpatient Table:
| Fields | Data Type | Relationships |
| pid | Varchar(5) | Primary Key |
| date | Date/Time | Not Null |
| labno | Varchar(5) | Foreign Key |
Room Table:
| Fields | Data Type | Relationships |
| room_no | Varchar(50) | Primary Key |
| room_type | Varchar(10) | Not Null |
| status | Varchar(10) | Not Null |
Bill Table:
| Fields | Data Type | Relationships |
| bill_no | Varchar(50) | Primary Key |
| pid | Varchar(5) | Foreign Key |
| patient_type | Varchar(10) | Allow Null |
| doctor_charge | int | Not Null |
| medicine_charge | int | Not Null |
| room_charge | int | Not Null |
|
int | Allow Null |
| no_of_days | int | Allow Null |
| nursing_charge | int | Allow Null |
| advance | int | Allow Null |
| health_card | Varchar(50) | Allow Null |
| lab_charge | int | Allow Null |
| bill | int | Not Null |
E-R Diagram
An entity-relationship diagram is used in modern database software engineering to illustrate the logical structure of the database. It is a relational schema database modeling method used to model a system and approach. This approach commonly used in database design. The diagram created using this method is called the E-R diagram.
DOWNLOAD NOW