Re: Hospital ERD

Thinking people typically do not rely on diagrams.

"Portroe" <fb_at_oooi.com> wrote in message news:bvqi77$sea$05$1_at_news.t-online.com...
> Charge Nurse, Medical Director, personnel officer, Doctor etc of course
> all have differing functions, and differing interactions with the other
> attributes
>
> the Charge nurse will have hundreds of connected records over a month,
> ie. medication ordered, The Medical director significantly less etc
>
> is there a source for Sample ERDs where I can see how people typically
> cope with multiple subclasses 'diagramatically' ?
>
> thanks
>
> Louis Davidson wrote:
> > Well, what are your requirements for each of the staff? What will you
need
> > to do with each of the different types of staff members? And how much
data
> > do you plan to store on each.
> >
> > My initial reaction is to say use a subtype construct. Have a Staff, or
> > person table that models common things you know about a staff member
> > (employee Id, badge number, physical attributes, etc) and then a
separate
> > table for specialized attributes about each type of staff member. I
would
> > expect it to be an incomplete subclass, in that some types of staff
members
> > might not have specialized attributes (janitors, possibly) while nurses,
> > doctors, etc might have specialties, etc.
> >
> > It is flexible, and most of all, it allows you to treat a person as
special
> > when needed, and as common when needed. If you have one table per staff
> > member type, then you might need a bunch of relationships to model that
they
> > all get ID cards, or whatever.
> >
>
Received on Wed Feb 04 2004 - 17:59:46 CET