tfn.comAllenbrook Inc.
Visual Internet Connection (VIC) software
Pioneer State Mutual Insurance Co., Flint, Mich.
BenefitPoint Inc.
Transaction-based e-commerce services
American General Financial Group, Neptune, N.J.
BISYS
Agent-based sales outsourcing agreement
New York Life Insurance Co., New York
Chesapeake System Solutions
Account transaction verification software
Trustmark Insurance Co., Lake Forest, Ill.
Firepond
Sales performance technology
Blue Cross Blue Shield of New Jersey, Newark
Fiserv Inc.
Outsourcing agreement for policy, billing,
claims and statistical reporting systems
American Skyline Insurance Co., Baltimore
Healthaxis ImagingServices
Imaging and data capture services
Trustmark Insurance Co., Lake Forest, Ill.
ImageRIGHT
Document management and automated
workflow software
Jewelers Mutual Insurance Co., Appleton, Wis.
Republic Group Underwriters, Dallas
Security Mutual Insurance Co., Ithaca, N.Y.
Metcom Excess, Cliffside Park, N.J.
CJW & Associates, Orlando
Mountain West Farm Bureau Insurance Co.,
Laramie, Wyo.
Insurance Services Office
Personal injury claims management solution
Zurich Financial Services, United Kingdom
Insurance Technologies
Point-of-sale management software
Allianz Asia Pacific/First Life Korea, Seoul,
South Korea
IVANS Inc.
Real-time transaction data exchange
AMS Services, Windsor, Conn.
Mercator Software Inc.
Health Insurance Portability and Accountability Act (HIPAA) compliance software
American National Insurance Co., Galveston, Texas
Mitchell International Inc.
Claims information management services
Beech Street Corp., Lake Forest, Calif.
RealMed Corp.
Claims resolution technology services
Blue Cross Blue Shield of Illinois, Chicago
Sengen
Web site redesign program
PMA Re, Philadelphia
SunGard Insurance Systems
Pension and annuity administration system
Old Mutual Employee Benefits (OMEB), London
Clarification: An article in the October issue, "Coming Clean With Data Quality," did not accurately explain a glitch in stored data at MetLife. As noted, MetLife's systems analysts discovered that, due to a systems default, customers on a particular source database were identified as having either "0" or "9" automobiles. Fortunately, for both MetLife and its customers, this database was being used by another line of business for other products and not, as was stated in the article, for MetLife auto policies.
