Lookup tables

  • Yikes, this gives me nightmares.  Once again, the "patient relationship to insured" rears its ugly head. 

     

  • Thats because I'm an Evil Devloper!  and our beloved database team insists on this structure.  What do you use that allows you to sleep peacefully at night?

  • I just got away from the healthcare industry.  Haven't ever slept better.  Your question reminded me of a HIPAA-compliant claims clearinghouse I built.

    More exceptions than rules.

     

    Have Fun!

    jg

     

  • I feel compelled to respond that healthcare is a wonderful place to be <g>!! Sleep is over-rated anyway.

    Thanks for the help.

    Sam

  • Sam,

    Bill has a nice design but I noticed in your earlier post you require the code value to be unique due to referential integrity requirements.

    To meet this need, you will need a constraint on the table Bill suggests.  Basically, reject a record that has a value in the CODE field that does not exist in your foreign table.  Look into constraints and triggers to see which suits your situation best.  I'd guess a constraint.

     

    Good luck.

     

Viewing 5 posts - 16 through 19 (of 19 total)

You must be logged in to reply to this topic. Login to reply