Jess

Re images etc: a lot depends on how you plan to present your data. We used to retain blobs in our database. IN SQL server you see MASSIVE bloat during that. Now we store stuff in folders on the server and dish it up using HTTP servers and/or Intranet Servers. VFP does this just fine- actually we zip/unzip on the fly as well to control network utilisation.

As for data; Labs and stuff are well understood, but if you are aggregating from several labs, reference ranges will differ and you need to allow for that.

Other Clinical opinion is not well-suited to relational database storage. Much of it is richly circumstantial and textually based- for example, the discovery of a WWII bullet adjacent to a knee being replaced is unlikely to have a field or lookup value(!) but needs to be recorded.

Have a look at our website ( www.platocis.com ) there may be a few ideas there. If you need a hand, I'll be in New Zealand for the next week or so, do you want to pop to australasia for some site visits? Glad to host you if you want to come, or in the UK after that...

Regards

JR