View Single Post
  #3  
Old December 6th, 2005, 02:42 PM posted to microsoft.public.access.tablesdbdesign
external usenet poster
 
Posts: n/a
Default HELP.. me please

Hi Jeff,

Thanks for your prompt response... I was well amazed)

Let me clarify your questions.

Surgery Name is the name of the Medical Practice e.g. Hillsgrove
Medical Surgery (Like Compnay name). The Surgery may have many doctors
and hence it might be better to break down the table into 2: tblDoctor
: DoctorID, DoctorFirstName, DoctorSurname and tblPractice :
PracticeID, PracticeName, PracticeAddress etc (I used Surgery rather
than Practice above). But I did not see the need to break it down for
just the doctors name.

This DB is directed to only the pateints that have a long medical
history and have repeated prescriptions. As most of these patients will
have their medicine delivered to them, the pharmacy provide a service
to re-order the prescriptions as needed. The aim of the DB is to be
able to run a daily report to show which patients require medicine to
be re-order from the doctor on that day and from which surgery. The
pharmacy will then order the prescriptions as needed.

e.g

Person A has 5 items, each having a differnt re-order date. Item 1 has
to be re-ordered today and is requested by the pharmacist. When this
prescription arrives at the pharmacy, the record will be updated with
the new re-order date (depending on the quantity prescribed).This will
happen for each and in some cases there may be a need to add/ remove
items as the treatment may change. So in effect, the patients don;t
have to worry about going to the surgery each time and having to
remember when to re-order as all this is done for them.

So the obove tables are not needed as all that info is on the standard
system already

I hope this explains your questions.

Many thanks.

PS thanks for the advise about regulations. I will get this verified
from the pharmacy.