Latest output (probably not in 4NF/5NF), rip it apart...

(I probably should add that the goal of this exercise is not to learn relational database design. I'm teaching myself Adobe AIR and need a target db to try out some transactions on.) *covering my ass*

Edit: Finally found out how to use ie notation.

By your design, one patient can only have one address - is this correct?
Can you rty explain the relationships in words in the following format

One/many _____ can have one/many _____ .

One patient can have only one address, but one address can be related to one/many patients. (e.g. a family)

One patient can have zero/many notations and one particular notation is related to only one patient.

One user is associated with zero/many notations and a particular notation is entered by only one user.

(I haven't figured out how to do cardinality in the design tool I'm using and I'm trying to get crow's feet notation working.)

Is a user the same as a patient?

Nope, a user would be a nurse or a doc. The idea is to create a simple application that could be used in a private clinic (one doctor and two nurses).

From the start I also had username and password in the table user but then I figured that perhaps it was better to have a separate password file (xml) for the whole application instead. The thing about AIR is that it uses an internal SQLite database and the db-file is bundled together and distributed with the application.