Sola
Registered User.
- Local time
- Yesterday, 20:58
- Joined
- Jun 1, 2007
- Messages
- 14
Hey, all. I am looking for some feedback before I start building. I am designing a database to log complaints against doctors and perform followup. The tables and abbreviated fields are:
tblComplaint: ComplaintID, ComplaintType, ComplaintDetails, ComplaintResolved
tblDoctor: DoctorID, DoctorName, DoctorContactInfo
tblPatient: PatientID, PatientName, PatientContactInfo
tblFollowUp: FollowUpID, FollowUpType, FollowUpDetails
I see two options for the db structure.
The first option is to put DoctorID, PatientID and FollowUpID in tblComplaint so that the one-to-many relationships have the "one" on the side of the IDs in the Doctor, Patient and FollowUp tables.
The second option is to put ComplaintID in the Doctor, Patient and FollowUp tables so that the one-to-many relationships have the "one" on the ComplaintID in tblComplaint.
My natural inclination is to use the first option, because it pulls all the relevant info together for each individual complaint. So, I guess my question is, is there any reason I should be considering option two instead?
tblComplaint: ComplaintID, ComplaintType, ComplaintDetails, ComplaintResolved
tblDoctor: DoctorID, DoctorName, DoctorContactInfo
tblPatient: PatientID, PatientName, PatientContactInfo
tblFollowUp: FollowUpID, FollowUpType, FollowUpDetails
I see two options for the db structure.
The first option is to put DoctorID, PatientID and FollowUpID in tblComplaint so that the one-to-many relationships have the "one" on the side of the IDs in the Doctor, Patient and FollowUp tables.
The second option is to put ComplaintID in the Doctor, Patient and FollowUp tables so that the one-to-many relationships have the "one" on the ComplaintID in tblComplaint.
My natural inclination is to use the first option, because it pulls all the relevant info together for each individual complaint. So, I guess my question is, is there any reason I should be considering option two instead?