I think the correct data model would have one table for Claims, one table for Insurances and one table that contains the many-to-many relationship of Claims to Insurances:
Claim - Insurance
This way, you won't have any synthetic tables and you will only have one instance of each Insurance in the master Table.
Upgrade your Qlik skills with my book QlikView Your Business: An Expert Guide to Business Discovery with QlikView and Qlik Sense
Not quite clear, trying to guess...
So, there are claims, and there are insurances, and I assume it could be Primary and Secondary insurance, hence InsId1 and InsId2. If my guess is correct, I'd use only one InsId in the Insurance table, only ClaimId in the Claim table, and a table in between to connect these, call it for example Claim_Insurance, with the fields:
InsId (link to Insurance)
ClaimId (link to Claim)
InsType (Primary or Secondary)
If I didn't guess right, provide more info please.