Clinic Management System

Actually the question is does my class diagram represent a good clinic management system in terms of the attributes and the relationships between objects.

Example:
some nurse can be assign to the department.
other nurse can be assign to the ward.
Conclusion:
Therefore it is not necessary to bind a nurse to a department.

Eugene - it depends on your business domain.  I would hazard a guess that a nurse has a department she reports to administratively, but is assigned to different wards over time.  This would mean the Nurse is a member of the Department and is assigned to a particular Ward.  Given this, I would associate the Nurse with both, with the Department relationship being an "employeeOf" type relationship and the Ward being a "currentAssignment" relationship.

If you have other questions or concerns, let me know.
Mark

A quick look at your diagram and there are other things I would fix - e.g. a Visit is an Event that is remembered. It should be associated with more than the Patient - e.g. what is the location that was visited? Who helped the Patient (Nurse, Doctor, ...)?

Sorry for another post - there are a number of other things I'd do: a Patient is-a Person...but a more flexible model has Roles that the Person can take on.  E.g. a Person has-a PatientRole and an EmployeeRole (for Patients that also work at the hospital or doc's office)

HTH, Mark

Visit (Outpatient)
Patient -> visits -> doctor -> ConsultationRoom
nurse -> ConsultationRoom
So a nurse and patient cannot be in the ConsultationRoom and the Ward at the same time.
Is this practical?.

I got it.

Doctor provides consultation to patient.

Entities
1. Doctor
2. Consultation
3. Patient

Consultation is link to ConsultationRoom
Nurse is link to the ConsultationRoom

I will redraw the ER diagram and post it.

Well, i assume the CR is in the Ward? or somewhere else... so it would be composition relationship (i.e. contained obj cannot exist w/o container obj).
The Event would document where, when, who, ... that actually took place. If your biz rqmts mean that you need to know the exact CR, then that is the where - does NOT mean the Nurse, etc are still there!  An Event is a historical object - it records the facts at the time.  Doesn't require the facts to stay the same.
Capische?

Patient and Doctor and ... have relationship to Visits - for the ones they participated in.

Room will have the following attribute:
RoomID
RoomType - Single Bed (1 patient only), Multi Bed (2 patient only)

Also I missed another relationship. Hospital and Department relationship. 1 Hospital can have many departments.

I Include herewith the updated class diagram.

Not to be crass, but if you want to add some more points I'll spend more time on this.  Otherwise, I believe you've made some progress and I'll wish you well.

ok :)

I also spotted a problem. The admission should be linked to bed.

I have done further updates.

Further improvements applied.

Small point, but I assume a Hospital has 1 or more Wards.
What questions/concerns do you have at this point?

The association between patient -> admission -> bed
Also since the doctor has a schedule, therefore can a schedule entity be created as a reference to fix an appointment with a doctor?

Oh, absolutely a doctor can have an appt on a calendar. Be aware that most frameworks have Calendar classes already.  So that part is probably taken care of, but you can still show a Calendar association and then Appointment objects.
So:   Doctor 1 --  0..*  Appointment 0..*-- 1 Patient

An Admission is an Event much like a Visit, just different relationships.

Also in between the nurse and ward I can have a duty roaster. Which nurse is in duty for a ward.

Duty
------
DutyID
NurseID
WardID
DutyDate
StartTime
EndTime

But then the limitation is that because of the attribute duty date, I need to enter the data many times.

Also I think the skills entity can be removed. I can include the attribute SkillDesc attribute inside the nurse and doctor entity. So from a user interface point of view, either this value can be typed or selected from a combo box.

I attach herewith the latest class diagram.

How can a visit and appointment be associated with a treatment?.

I carefully relook at my diagram and now I understand :)
However is it advisable to have a status attribute inside the visit class?
status: Arrived, Visited, Left