Please start any new threads on our new
site at https://forums.sqlteam.com. We've got lots of great SQL Server
experts to answer whatever question you can come up with.
| Author |
Topic |
|
coldfiretech
Starting Member
30 Posts |
 Posted - 2009-04-12 : 23:14:33
|
| I am working on a project now where i have to store medical information.Does anyone here have any information regarding how I should be storing medical information in my database.. I am storing medications, alleriges, disabilites, ect... All linked on the ProfileID which is uniqueidentifier.My table structure is like this[Profiles][id (PK uniqueidentifier) / ProfileName (varchar(60)][Allergies][id (PK uniqueidentifier) / ProfileID (fk on id field in profiles table)]I have several more tables setup with this structure.Should the data be encrypted some how or should the profileids just be encrypted and if so, how could i go about doing this.thanks-MattSucess comes before work only in the dictionary. |
|
|
visakh16
Very Important crosS Applying yaK Herder
52326 Posts |
Posted - 2009-04-15 : 13:19:53
|
| why using unique identifiers as pk? any problems in using identity columns? |
 |
|
|
SwePeso
Patron Saint of Lost Yaks
30421 Posts |
|
|
coldfiretech
Starting Member
30 Posts |
Posted - 2009-04-18 : 12:34:08
|
| what does a link for Normalization Rules have anything to due with storing medical information.. Thanks, but obviously neither one of you want to help, if you just want to criticise dont bother even replying to the post.. waste someone elses time.Sucess comes before work only in the dictionary. |
|
|
|
SwePeso
Patron Saint of Lost Yaks
30421 Posts |
Posted - 2009-04-18 : 14:29:07
|
If you read the link carefully, you would have known how to design your project.1. Make a Profiles table (ProfileID (pk), ProfileName)2. Make an Allergies table (AllergyID (pk), AllergyName)3. Make a ProfileAllergies table (ProfileID (fk), AllergyID (fk))4. Make Disabilities table (DisabilityID (pk), DisabilityName)5. Make a ProfileDisabilties table (ProfileID (fk), DisabilityID (fk))Or...1. Make a Profiles table (ProfileID (pk), ProfileName) -- coldfiretech 2. Make an IllnessTypes table (IllnessType (pk), IllnessTypeName) -- Allergy or Disability3. Make an Illness table (IllnessID (pk), IllnessName, IllnessTypeID (fk)) -- Strawberries or Hearing4. Make a Deficiencies table (ProfileID (fk), IllnessID (fk))If you don't understand the information we provide, plese be courteous and tell so, instead of trying to insult us.quote:
Originally posted by coldfiretech
what does a link for Normalization Rules have anything to due with storing medical information.. Thanks, but obviously neither one of you want to help, if you just want to criticise dont bother even replying to the post.. waste someone elses time.
Also, we can't decide for you wether or not to encrypt you data. It's your business rules.We can however tell you about pros and cons using encrypted data.
E 12°55'05.63"N 56°04'39.26" |
|
|
|
nathans
Aged Yak Warrior
938 Posts |
Posted - 2009-04-19 : 16:20:47
|
| Ease up Matt... both Visakh and Peso are stellar members here and are genuinely trying to help. |
|
|
|
coldfiretech
Starting Member
30 Posts |
Posted - 2009-04-19 : 21:21:20
|
| Nathans,Genuinely trying to help?? I dont think so.IF they would have read my post, it states that I ALREADY have my table structure. I dont need help making the tables. I was looking for ADVICE on storing medical data.. I was NOT looking for critism about how I designed my tables or what column types I use. Secondly, I wasnt insulting anyone. Meerly stating that if your not going to reply to the post with an answer that pertains to the question why waste the time.Sucess comes before work only in the dictionary. |
|
|
|
SwePeso
Patron Saint of Lost Yaks
30421 Posts |
Posted - 2009-04-20 : 03:04:21
|
I gave advice how to efficient store medical data (part #2 of previous post).That is not the same as give advice wether or not to encrypt the data. That's another layer.As a rule of thumb, when encryptig the data (and you should use salt) any index practically renders useless. That's one drawback of encrypting.The positivie side is that data is more secure IF the database should fall into wrong hands.
E 12°55'05.63"N 56°04'39.26" |
|
|
|
|
|
|
|
|
Storing Medical Data