Hi,
It seems that it is a kind of DSS (Decision Support System). Having in mind
what Ed Loher told about the data model techniqus and different ERD, DFD or
flow charts, In my opinion you should first set the goals. I mean your
project may contain two parts. First part contains tables and the data
inside them. The second part is a rule base system which is perhaps a kind
of mathematical modelling technique used to optimize the scheduling problem
due to the goals.So I think It would be better if you first try to define
the exact real word problem , setting the goals, choosing the right math
model and then starting to design the data model.
There is a broad branch of apply mathematics called OR ( Operation Reseach )
talking about differnt math modelling techniques and associated computer
softwares.
HTH
Omid Omoomi.
>From: "Barnes" <aardvark@ibm.net>
>To: <pgsql-general@postgreSQL.org>
>Subject: [GENERAL] scheduling table design
>Date: Wed, 23 Feb 2000 11:48:19 -0500
>
>
>I'm trying to build what amounts to an appointment book for a doctor's
>office. The office has multiple doctors, and my application is going to
>handle patient appointment scheduling for all the doctors(among many other
>things). Anyway, I am looking for advice on database table design.
>
>I'll be tracking the date and time of the appointment, the doctor, reason
>for the appointment, insurance company authorization and the patient's
>name.
>I'll also need to be able to view open appointment blocks, and I would like
>as much flexibility as possible in setting the times of appointments.
>
>If anyone has any suggestions or advice regarding table design, I would
>really appreciate it. I'm not sure at all where to start. With things
>like
>open appointments, this seems much more complex than the typical name,
>address, phone number databases I've done in the past.
>
>Thank you for any help.
>
>David Barnes
>
>
>************
>
______________________________________________________
Get Your Private, Free Email at http://www.hotmail.com