I also think you need to stop and fix the design issues.
First, the naming issues:
---------------------------
Object names
should be letters and numbers.
Do not begin an object name with a number.
NO spaces, punctuation or special characters (exception is the underscore) in object names
Object include Field names, table names, query names, form names and report names.
In a relational database, generally 1 table holds info (attributes) of one "thing".
In the doctor table, first name, last name, address all help to "define" a "doctor".
Is the "AssistantID" an attribute of a doctor?
How about the "Station_ID"?
How about a "ShiftID"?
What about "DoctorBreaks"??
So those 4 "things" (plus 2 others) should be in another table (the junction table).
The same goes for the Nurse table.
Does/can a nurses position change over the course of a day/shift? With the current design, if you change the nurse position, the previous position is lost.
StationID?
ShiftID?
BreaksID, LunchID, WorkHrsID?
So it looks like you will be in need of several junction tables.
I also noticed there is not one date/time field in your dB. Wouldn't the date/time a doctor/nurse assisted a patient be important?
Something to think about.......