Payment integrity Knowledge Center
Centene · payment integrity
Knowledge Center/Search the index
Retrieval

Search the policy index

The same retrieval the claim screen runs, driven by hand. A query is embedded with the model the dataset was ingested with, and compared against every chunk inside the scope — organisation, project, dataset and policy version. Nothing outside that scope is reachable from here.

32 chunks · local-hashing-256 at 256d

What this is doing

Every chunk in the index carries the organisation, project, dataset, document and version it came from, plus an is_active flag. A retrieval filters on all of them before it scores anything — the platform's own design notes call isolation the top risk on a shared collection, and the filter is not optional on any path here.

Try billed units administered dose against the current version and then against v1.4: the same question returns the rule that was in force at the time, which is the whole reason the superseded version is still indexed.