it make sense. as an intermediate step, perhaps could be used for
internal (doctor-doctor, nurse-doctor,...) "distributed" use,
besides the "call-center-like" use.
the table disign should be easy. scheduling itself can be just
one or two (if support complicated feature) tables. So, just
use your common sense (unless you really like it, no need for
formal data modeling). A dirty way to do it (and this project
is a very good one being dirty ;-) is put everything in one table!
then, if you feel too filthy, consider split it into two (ok,
that is modeling). You can ask help by showing the prototype
design and your concerns.
Also, there is some OSS schedular/time sheet there if you like
to surf. Somebody (like me ;-) may have done the schedular but
not authorized to publish them here. By put your prototype here,
people can help freely.
Some thing you really need to pay attention are:
make sure use datetime and timespan datatype. do not use date or anthing else.
also, be sure use serial type (or use a standard technique that do
not use sequence or serial feature of the database -- so that the app
can be portable among different dbms. But seems that it's not very often
used and I do not really understand it. you can search the archive of
this list. it's called hi-lo algorithm ;-)
On Thu, 24 Feb 2000, Barnes wrote:
> Yes, it is a tool for the support staff to handle scheduling. I would be
> very reluctant to allow patients to use an appointment scheduling tool for a
> doctor. People who aren't trained tend to do unpredictable things, whether
> intentionally or accidently, and while I won't rule out the ability to
> someday see openings in the schedule and insert an appointment from the
> Internet, I think the potential risks are high. Someone with an ill founded
> sense of humor might decide to fill in a hundred appointments for Mickey
> Mouse, which would be expensive.
>
> What do you think?
>
> David Barnes
> aardvark@ibm.net
>
> -----Original Message-----
> From: kaiq@realtyideas.com [mailto:kaiq@realtyideas.com]
> Sent: Wednesday, February 23, 2000 2:30 PM
> To: Ed Loehr
> Cc: Barnes; pgsql-general@postgreSQL.org
> Subject: Re: [GENERAL] scheduling table design
>
>
>
> On Wed, 23 Feb 2000, Ed Loehr wrote:
>
> > Barnes wrote:
> > >
> > > I'm trying to build what amounts to an appointment book for a doctor's
> > > office. ...
> > >
> so, it is used by office secretary, not patient directly? why not?
> I'm curious.
>
>
>
>
