logical mode + ER diagram

[fatima_7]

I need someone 2 help me drawing the ER diagram for this scenario :(

Draw an ER Model and the corresponding relational model (logical model) for the following problem.

StrongTEETH4U is a private dental clinic that is well known and has an excellent reputation in the area. All patients in the clinic have their details stored in a ClinicBook database. This database is used by the dentists and secretaries in the clinic to contact the patients for their routine checking and remind them of their appointment dates. A patient has a patient number (a unique value), first name, surname, house/flat number, street, city, P.O. Box, telephone number, a first admission date to the clinic, the date of next appointment (if any!), and the dentist ID that has treated the patient. Patients have to register when they first attend by calling in to the clinic and provide a secretary with their details. Patients have to have appointments created for them by dentists and secretaries in the clinic before they can be seen or treated, and the date of the appointment along with the other required details is stored into the ClinicBook database. Doctors have an ID, first name, surname and specialism e.g. teeth implant.

[fatima_7]

logical model***

[fatima_7]

I really need help :(

[JamesCherrill]

You know the rules: we only help people who are showing some effort.
Show what you have done so far, explain what's stopping you going further, and someone wil help.

[Reverend Jim]

Posting the same question over and over is not going to get the results you want. What it WILL do is get you infracted. Play nice.

[Tarek_2]

I will assume that this is your first try and you are new to this so let's start together :

StrongTEETH4U is a private dental clinic that is well known and has an excellent reputation in the area. All patients in the clinic have their details stored in a ClinicBook database. This database is used by the dentists and secretaries in the clinic to contact the patients for their routine checking and remind them of their appointment dates.

All this part is a simple description of the system, we can understand that there are patients and dentists. Let's see farther.

A patient has a patient number (a unique value), first name, surname, house/flat number, street, city, P.O. Box, telephone number, a first admission date to the clinic, the date of next appointment (if any!), and the dentist ID that has treated the patient.

Patient and his attributs, one Entity. A unique value means it's the primary key.

Patients have to register when they first attend by calling in to the clinic and provide a secretary with their details.

I don't see any additional data in this part.

Patients have to have appointments created for them by dentists and secretaries in the clinic before they can be seen or treated, and the date of the appointment along with the other required details is stored into the ClinicBook database.

Some tricky parts : is the appointment a Relationship or an Entity, it does not have a proper primary key, it requiers a Patient and a Doctor, so, it can be a Relationship.
In this case, the "Appointment date" must help us to keep the history of all Appointments.
The part is stored into the ClinicBook database is another nosens, DON'T CREATE AN ENTITY CALLLED DATABASE.

Doctors have an ID, first name, surname and specialism e.g. teeth implant.

"Doctors" means "Dentist", don't create a new Entity, juste fill the Dentist with these attributes.

It's a start, some points need an additional work.