Short answer: For insurance claims intake, use a staged retrieval architecture with explicit collections, bounded queries, and source context that identifies the exact document revision; re-index changes deliberately, delete withdrawn records, and test retrieval quality on a small labeled set before production.
The central trade-off is retrieval quality versus latency. For claims intake, I would spend a little latency on a deterministic revision gate before vector search, because a fast answer grounded in superseded evidence is still the wrong answer. Keep that gate outside the provider boundary. It should decide which revisions are eligible; the search service should rank only those eligible records.
This boundary also makes provider choice less dramatic. Pinecone, Weaviate, Qdrant, pgvector, and Infrai can all sit behind a narrow retrieval contract, while the claims system remains responsible for version identity, deletion, freshness, and answer traceability.…