Re: Design problem and suggestions...
From: Jeff Boyce (JeffBoyce_IF_at_msn.com-DISCARD_HYPHEN_TO_END)
Date: 02/13/05
- Next message: Dave: "print database fields"
- Previous message: Jeff Boyce: "Re: relationship help"
- In reply to: onedaywhen: "Re: Design problem and suggestions..."
- Next in thread: onedaywhen: "Re: Design problem and suggestions..."
- Reply: onedaywhen: "Re: Design problem and suggestions..."
- Messages sorted by: [ date ] [ thread ]
Date: Sun, 13 Feb 2005 06:31:09 -0800
I suspect that the reason for considering that all those roles mentioned as
roles of persons is that any system would have to handle the exception. You
mentioned that it would be rare for an employee (?nurse) to also be a
patient.
I disagree, and point out that it only takes one to break a system that
doesn't handle that. How many nurses (or administrators, or doctors, or
x-ray techs) have a primary physician, who they see for wellness, for their
blood pressure or diabetes, or following a skiing accident, or ...?
-- Good luck Jeff Boyce <Access MVP> "onedaywhen" <jamiecollins@xsmail.com> wrote in message news:1108119243.047726.309900@o13g2000cwo.googlegroups.com... > Mike Sherrill wrote: > > >I think this would only have > > >limited advantages in the data model described. > > > > Think about it some more. > > > > To your "Doctor" entities and "Patient" entities, add "Nurses", > > "Pharmacists", "X-Ray technicians", and "Administrators". Let one > > administrator also be a doctor, and another administrator also be a > > nurse. Let them all be patients. > > In the healthcare scenario, I don't foresee much of an intersection > between Employees and Customers i.e. what percentage of patients are > employees of the healthcare provider? how much information is common > to both at the base level? Employees and Customers are modelled as > separate entities in the Northwind example database supplied with MS > Access and I would expect a typical newsgroup post to aspire to a > similar level of abstraction. The approach to which you elude is more > suited to OOP in the front end application than the relational model. > Doable but what is gained, I wonder. > > > Then start recording their > > addresses and phone numbers. > > Are a doctor's address and a patient's Address the same entity? Yes in > the physical sense but perhaps not in the data model. In my country, I > suspect Data Protection legislation (i.e. right of access to > information rather than database security) would require a greater > degree of physical separation. > > You approach is interesting and thorough, though. Please post your > basic DDL so we can see how if measures up. > > Jamie. > > -- >
- Next message: Dave: "print database fields"
- Previous message: Jeff Boyce: "Re: relationship help"
- In reply to: onedaywhen: "Re: Design problem and suggestions..."
- Next in thread: onedaywhen: "Re: Design problem and suggestions..."
- Reply: onedaywhen: "Re: Design problem and suggestions..."
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|