On 03.01.2009, at 21:24, Jeff Mar wrote:
1. What does normalize mean in this context?
You should get an introduction book for database design. "Database Design for mere Mortals" was okay. If you don't get the database model right you will have a lot of pain later.
5. Do you consider using complex ID's? i.e. 00123.00101 so MR is 00123, with the .001 meaning 1st admit and the .00001 meaning outpatient (vs IOP vs Full day treament)? This passes three pieces of info and then I can use calculations in foreign tables to break it down into three different pieces. It had seemed like this might at times be useful for go to related records as it would differentiate each admission by sorting on a single field and yet I could use the calculated result as a find field when I want by medical record number. This may be more complex than just scripting finds to include multiple criteria.
Always use dumb numbers. Don't code your business logic into the design of the database.
Perhaps the following could help: don't try to do the complete database in one go. Concentrate on one area that you can isolate a bit and implement this.
Will your IT people support a Filemaker solution? How many users do you plan to have? How many sites?
Mit freundlichen Grüßen/Regards Trixi Willius http://www.mothsoftware.com Mail Archiver X: archive, clean and search email http://www.beatrixwillius.de Fractals, 3d landscapes etc.
