Patients - Orders - OrderDetails - Products
v v
| |
Practices -------------- Doctors


The thing that strikes me in this discussion, unless I missed it, is that
there is no transaction histroy but the update of a datre field ... should
there be ?

i.e.

Patients - Orders - OrderDetails - TransactionHistory
v v v
| | |
Practices - Doctors Products

Is each line that a doctor writes on one percription in effect not a separate
perscription? I guess what I am am saying is that it may just be simpler for
your design needs to have each record be a perscription rather than grouping
them by orders - then anything can change and you won't have to split an
order into two orders to handle differences in the future.

To make entry quicker you could update the default value of a field to be
that which was entered in the previous perscription record. Or have a
perscirption copy button on a form that creates a duplicate perscription, the
user would then edit it as needed.

i.e.
Products
^
|
Patients - Perscription - PerscriptionHistory
v v
| |
Prctices ----Doctors


Just a thought,
Roger

--
Message posted via http://www.accessmonster.com