UML Class Diagram For Hospital

The description for the UML class diagram as follows,

Ward is a division of a hospital or a suite of rooms shared by patients who need a
similar kind of care. In a hospital, there are several wards, each of which may be
empty or have on it one or more patients. Each ward has a unique name. Wards are
also differentiated by gender of its patients, i.e., male wards and female wards. A
ward can only have patients of a particular gender admitted to it. Every ward has a
fixed capacity, which is the maximum number of patients that can be on it at one
time (i.e., the capacity is the 50). Different wards may have different capacities.

The doctors in the hospital are organized into teams. Each team has a unique name
or code (e.g., Orthopedics or Pediatrics) and is headed by a consultant doctor. The
consultant doctor is the senior doctor who has completed all of his or her specialist
training, residency, and practices medicine in a clinic or hospital, in the specialty
learned during residency. She or he can supervise medical students.

The rest of the team are all junior doctors. Each doctor could be a member of no
more than one team. A Patient is treated by one doctor. The entire team is also
responsible for each patient treated by any doctor on the team. However, the leading
doctor of the team is ultimately responsible for each patient.

Each patient has a patient record, which is provided when the patient is admitted.
The patient record has the patient id and details of the patient. Doctors can check
patient records whenever necessary. There are nurses in the ward. Each ward can
have up to twenty nurses. Nurses can update the patient record. The patient record
is discarded when a patient gets discharged from the hospital.

 

According to the above description , UML class diagram can be given as below,

 

 

Below shows the assumptions that I made for above UML Class diagram,

• Ward belongs to 1 hospital 
• Hospital has 1 or more wards
• Ward doesn’t exist without hospital 
• Team doesn’t exist without hospital 
• Team belongs to 1 hospital 
• Hospital has 1 or more teams 
• Ward has 1 or up to 20 nurse 
• Nurse works in only 1 ward 
• Ward has 0 or more patients (up to some maximum value that ward support) 
• A patient belongs to one ward 
• Patient record update by 1 nurse 
• A nurse update one or more patient records 
• Only nurse knows the record 
• A team headed by 1 consultant doctor 
• A consultant doctor head 0 or 1 team 
• Both team and head knowing each other 
• A doctor member of 1 team 
• A team has 1 or more doctors 
• Doctor doesn’t exist without team(Because in the paragraph says doctors in the hospital organize in to teams) 
• A team responsible for 1 or more patients 
• Only a team knows the patient 
• A doctor treats to zero or more patients 
• A patient treated by only one doctor 
• A patient ultimate responsible by only one consultant doctor 
• A consultant doctor ultimate responsible for 0 or more patients 
• Only consultant doctor knows the patient 
• A doctor checks 0 or more patient’s records 
• A patient’s record check by 0 or more doctors 
• Patient’s record doesn’t exist without patient 
• A patient has only one record 
• A record belongs to only one patient 
• Junior Doctor and Consultant Doctor are sub class of Doctor Super class 
• Ward depends on Gender 
• Patient Depends on Gender 
• I got all the classes attributes , operations as public