Posted: Sat Dec 17, 2005 7:00 pm
actually, em.
of all the things you mentioned, I was not a priest. but you forgot the other 30+ things i have done.
officially, I am a data architect and technical compliance professional consultant.
i am currently working in two aspects : energy market data provision & federal and environmental regulation compliance.
this could be VERY long term...
now, back to your database.
you don't have to make a full bells and whistles flowchart... jst make a school-like outline. I can mark it up from there.
Why did you move from the structure of:
Patient -
Pre-Surgery
Intra
Post-Surgery
Can I see that one? Maybe it will help me wrap my head around the database you already sent.
And Pete... that's good advice (especially about autonumbers... having auto numbers to creatwe relations between tables is a BAD idea), but some of it is hard to implement for long term flexibillity, in this case. Not to mention some of it doesn't apply to em's case.
I see no room for contingency in here, which is never good when it is a customer database capturing long term relationships.
of all the things you mentioned, I was not a priest. but you forgot the other 30+ things i have done.
officially, I am a data architect and technical compliance professional consultant.
i am currently working in two aspects : energy market data provision & federal and environmental regulation compliance.
this could be VERY long term...
now, back to your database.
you don't have to make a full bells and whistles flowchart... jst make a school-like outline. I can mark it up from there.
Why did you move from the structure of:
Patient -
Pre-Surgery
Intra
Post-Surgery
Can I see that one? Maybe it will help me wrap my head around the database you already sent.
And Pete... that's good advice (especially about autonumbers... having auto numbers to creatwe relations between tables is a BAD idea), but some of it is hard to implement for long term flexibillity, in this case. Not to mention some of it doesn't apply to em's case.
I see no room for contingency in here, which is never good when it is a customer database capturing long term relationships.