Patient table
Visits table
Patient and Visits have a one to many relationship - One patient can have multiple visits. The patient table will have a patient id as the primary key and the Visits table will use the patient id as a foreign key. Hope this helps.
2007-04-30 09:52:44
·
answer #1
·
answered by sinkablehail1978 5
·
2⤊
0⤋
You need an entity, such as Hospital Employee. Each professional will have an identifier. This could be anything and totally arbitrary, but it must end up being unique for each one. For example, each new Health Professional could have an Employee Number. Each employee should have a type, (ie. GP, RN, LPN, Surgeon). You also need an Attribute, say ROLE, for each Health Professional like GP, RN, LPN, Thoracic Surgeon, etc. You also need an entity for Patient. Each patient must have a patient ID. Maybe SSN. Maybe the patient should have a payer type (ie. Self, Insurance, etc.) You need one for Room. You will also need associative entities which match the patient to the room, so you build an entity such as Patient-room. For that to work, you need a number for the room and a number for the patient. Then, for each patient, there can be only one room, creating a One-to-Many relationship based on the foreign keys of patient number and room number (there can be more than one patient in a room, but you will also want, in the ROOM table, a ROOM TYPE such as Private, Double Occupancy, Quad, ICU, and so on.
Does this help. I really don't think you have to work so much harder on this now.
2007-04-30 17:03:30
·
answer #2
·
answered by Kokopelli 6
·
2⤊
0⤋