insurance database

[george]

Hi to all,

I am developing an insurance database and I would like
some help if possible in designing my Policies table. In
insurance one can have many different types of policies
originating from different branches of the company, ie
Fire policies, Automobile policies, Life policies etc. All
types of policies share some common characteristics like:
Branch
ApplicationN
PolicyN
StartingDate
ExpiryDate
DateOfFirstIssue
etc
so I have created a table that comprises all types of
policy and contains the above mentioned information. The
problem is that there is also information that pertains
only to a particular type of policy and to no other type.
For example, automobile policies need to include
information about the insured vehicle, fire policies need
to include information about the insured house etc. I have
thought to create more tables like FirePolicyDetails,
AutomobilePolicyDetails etc and then to relate these to my
AllPolicies table. Is this a good thought? What kind of
relationship should I establish? Is there a better
approach?

thanks in advance, george

 

[Matt Fragale via AccessMonster.com]

George,

I know a thing or two about the insurance industry, since my wife works for
one of the larger companies and tells me things now and then that I don't
understand. LOL. This is something you're doing for a local insurance
agency, I assume, to keep track of your clients and their coverages?

Your idea seems to be correct, in that having tables for each type of
specific coverage would probably work, assuming you related that record to
the record of the overall policy. I'm not sure about that relationship
type, though. It would most likely be a one to many relationship with one
overall policy, and potentially, several vehicle policies or property
policies, or whatever other policies your company offers.

 

[Immanuel Sibero]

George,
Take a look below, if you havent found it already:

http://www.databaseanswers.org/data_models/insurance_brokers/index.htm

HTH,
Immanuel Sibero