Help With Design Structure

I'm currently working on a database for a Neurology department. It is is
somewhat of a complicated design (at least I think so), and so any input into
the design would be useful. We have a several stroke patients that come into
our lab. I have created a table for them called Demographics, of which,
PatientID is the primary key.

I want to now link this table to their treatment data, but there are several
constraints.

1) Depending on the type of stroke a patient has, they can be placed in a
different treatment. This is not a big deal, because I can filter diagnosis
type through using Access Queries.

2) There are seven different treatments in this lab. A patient can take more
than one treatment (though not at the same time). Each treatment has a unique
set of tests assigned to them. In addition, all the tests within each
treatment are administered at different time points (i.e. Baseline, Interim,
Post Treatment etc).

For example (treatment names are made up)

can take which has tests
which are given at
Patient -------------- Zizaparole ---------------------- A, B, C, D... ----
-------------------- Baseline, Interim...

It is important to note that ALL of tests A, B, C, D... are re-administered
at each session (Baseline, Interim) etc...

What would be the most efficient design? Any help would be useful.

Thanks,
Tejas

Hi Tejas,

You did a good job of describing the things you did describe but the
most complicated thing about your prospective design is that you
haven't fully defined what you want to have happen. We don't have the
parts you left out. They're the ones in your mind that were so
obvious to you that you didn't feel the need to share. :-)

I kind of think that you don't just want to record results but you
want to create some sort of scheduling application. Yes? No?

Access can be made to do things that look like Outlook but that isn't
native to relational databases so the designs require some unusual
gyrations.

Please post back with the whole of what you want to do - in real world
terms rather than Access terms. By the way, my offline reader
clobbers the formatting you tried to deliver in your post. It would
need to be a much slimmer screen size to be really useful. This that
I'm typing to you is perfectly justified on my display but it will get
clobbered by my reader. All full width lines will be truncated with
hard returns. If I were reading this in a web reader it would look
different.

I'm not in here every day so someone else may pick it up before I see
it again.

HTH
--
-Larry-
--

"Tejas" u42063@uwe wrote in message news:8110209f85b67@uwe...
I'm currently working on a database for a Neurology department. It
is is
somewhat of a complicated design (at least I think so), and so any
input into
the design would be useful. We have a several stroke patients that
come into
our lab. I have created a table for them called Demographics, of
which,
PatientID is the primary key.

I want to now link this table to their treatment data, but there are
several
constraints.

1) Depending on the type of stroke a patient has, they can be placed
in a
different treatment. This is not a big deal, because I can filter
diagnosis
type through using Access Queries.

2) There are seven different treatments in this lab. A patient can
take more
than one treatment (though not at the same time). Each treatment has
a unique
set of tests assigned to them. In addition, all the tests within
each
treatment are administered at different time points (i.e. Baseline,
Interim,
Post Treatment etc).

For example (treatment names are made up)

can take which has tests
which are given at
Patient -------------- Zizaparole ---------------------- A, B, C,
D... ----
-------------------- Baseline, Interim...

It is important to note that ALL of tests A, B, C, D... are
re-administered
at each session (Baseline, Interim) etc...

What would be the most efficient design? Any help would be useful.

Thanks,
Tejas