Skip to content
Start free
← All industries

Insurance applications

Connect claims
to their source evidence.

Build investigation, policy knowledge and service workflows with connected records and searchable documents.

Start with the relationships Discuss your workflow

The record, the wording, the supporting file.

Link a claim to the relevant policy version and supporting documents, retaining the source behind each result.

A claim file with source contextIllustrative application data
Claim file claim:017
Start with the claim

Keep the evidence attached.

For reviewer context
Structured record

Claim 017

Policy reference
policy:042
Involved party
party:006
Service case
case:011
Policy sourceVersion 3

Policy wording

document:082
Stored source locationSection 4

Retain the original text and version with each retrieved passage.

Supporting recordsLinked to claim:017
Inspection notedocument:018Revision 1
Statementdocument:026Revision 2
Contact notenote:011Revision 1
How the application assembles this file
  1. SQL: load claim fields and policy references.
  2. Graph: follow declared links to parties, documents and service cases.
  3. Vector + full-text: retrieve related passages and exact terms separately, then load source records.
Explore the retrieval pattern

Illustrative records. Your application maintains the source IDs, policy versions and document links.

5 use cases / Insurance

The right modalities for your workflow.

Start with the combination that fits your question. These are recommended starting points; the best fit depends on your data and query patterns.

Insurance: use cases, recommended query modalities and why each combination fits.
Use caseRecommended modalitiesWhy this combination fits
Claims operations

Track claims, assignments and outstanding review tasks.
SQL

SQL filters claims by stage, joins assignment records and calculates operational counts and elapsed times.
Connected claims investigations

Explore shared claimants, providers and insured assets.
SQL Graph

SQL narrows the claim cohort. Graph follows shared entities and relationships for an investigator to assess.
Claims evidence review

Connect a claim to its policy, parties and documentary evidence.
SQL Graph FTS

SQL retrieves claim details, Graph connects the policy and parties, and FTS locates relevant wording in the evidence.
Policy wording lookup

Find clauses and definitions in the relevant policy version.
SQL FTS

SQL identifies policy and revision metadata. FTS searches the indexed wording for exact terms and phrases.
Claims knowledge retrieval

Find related guidance and reference cases for a handler's question.
SQL FTS Vector

FTS matches terminology, Vector finds similar descriptions, and SQL provides source dates and case attributes for human review.

Combine query results in your application using shared record IDs. Keep text indexes and embeddings updated as the source data changes.

Choose how to find the evidence.

SQL

Claim and policy fields

Filter status, product, dates and source IDs.

 Graph

Parties and relationships

Follow declared links between claims and involved entities.

 Vector

Related document passages

Search embeddings supplied by your application.

 Full-text

Exact policy language

Match phrases, document titles and reference codes.

Implementation path

Make source references part of the model.

  1. 01 / Register

    Define the claim context.

    Keep claim, policy, party and document IDs, plus policy versions and source locations.

  2. 02 / Prepare

    Index selected documents.

    Write source rows, supply passage embeddings and index text through separate calls.

  3. 03 / Retrieve

    Assemble the evidence.

    Combine result IDs in your application, apply access rules and show the original document references.

Track source updates and index retries. Claim decisions remain part of your review process.

Follow the ingestion pattern

Start with a claim.
Keep its sources in view.

Build a first example Explore other industries