For AI agents: a documentation index is available at https://www.mongodb.com/docs/llms.txt — markdown versions of all pages are available by appending .md to any URL path.
Docs Menu
Docs Home
/ /
Example: Insurance Data Models
Docs Home
/ /
Data Modeling
/
Example: Insurance Data Models
Docs Home
/
Tools
/
Relational Migrator
/
Data Modeling
/
Example: Insurance Data Models

Refactor the Claim Domain

In this step, you will refactor the Claim domain by adding mappings for each related table in the relational database and embedding all claim-related information under a single MongoDB claim document. Since the Claim and Litigation domains are closely related, you will also recreate the many-to-many relationship between the two domains by referencing the Litigation entity from the claim document.

About this Task

The Claim domain includes the following key entities:

  • Claim: Claim for coverage or compensation

  • Claim Party Role: An associative entity which links the following entities:

    • Party

    • Party Roles

    • Insurable Objects

  • Insurable Object Party Role: An associative entity which links the following entities:

    • Party

    • Party Roles

    • Insurable Objects

Before You Begin

Refactoring the Claim & Litigation domain is the fourth step of the insurance data model example tutorial. Before you refactor the Claim & Litigation domain, ensure that you:

Steps

1

From the MongoDB view, click the claim document

On the right side of the screen, the Mappings menu opens.

2

Add mappings for the claim_party_role table

Next to Mappings from relational tables, click Add. Click Embedded array and select claim_party_role from the Source table drop-down menu.

Under the All fields checkbox, uncheck the claimIdentifier field and click Save and close.

3

Add mappings for the the insurable_object table under the claim document

Next to Mappings from relational tables, click Add and select Embedded documents. Choose insurable_object from the Source table drop-down menu.

Click Save and close.

4

Embed the policy_coverage_detail table within insurableObject

Policy coverage details help establish the link between claims and policies. To embed the information from the policy_coverage_detail table, click Add and select Embedded array. Choose policy_coverage_detail from the Source table drop-down menu.

Under the All fields checkbox, uncheck the insurableObjectIdentifier field, and click Save and close.

5

Map the many-to-many relationship between litigation and claim

Since Litigation is a separate entity, you just need to reference that entity from the claims document as an array of litigation identifiers.

Next to Mappings from relational tables, click Add and select Embedded array. Choose litigation_party_role from the Source table drop-down menu.

Under the All fields checkbox, uncheck the litigationIdentifier field, and click Save and close.

6

Remove collections that are no longer needed

Now that you mapped all the necessary tables to the claim collection, you can delete the claimPartyRole collections from the MongoDB view of Relational Migrator.

Next Steps

After you map the Claim domain, refactor the Litigation domain in a similar manner. See Refactor the Litigation Domain.

Back

Refactor the Policy Domain

Next

Refactor the Litigation Domain

On this page