Using Custom Search Parameters

Configure Search Parameters

You can control which search parameters are known to Vonk. This is managed in the same way as all the conformance resources, see Controlling the Conformance Resources.

Re-indexing for new or changed SearchParameters

Vonk extracts values from resources based on the available search parameters upon create or update. This means that if you already had resources in your database before adding a custom search parameter, those resources will not be indexed for that parameter. If you on the other hand removed a previously used search parameter, the index will contain superfluous data.

To fix that, you should re-index (repeat the extraction) for these parameters.


This is a possibly lengthy operation, so use it with care.


During the re-index operation, search results may be unreliable.

  • To re-index all resources for all search parameters, use:

    POST http(s)://<vonk-endpoint>/administration/reindex/all

    This will delete any previously indexed data and extract it again from the resources.

  • To re-index all resources for certain search parameters, use:

    POST http(s)://<vonk-endpoint>administration/reindex/searchparameters

    In the body of the POST, you put the parameters to actually re-index as form parameters:,Observation.code

    include means that resources will be re-indexed only for those search parameters. You use this if you added or changed one or few search parameters.

    exclude means that any existing index data for those search parameters will be erased. You use this when you removed a search parameter.

Remember to adjust the Content-Type header: application/x-www-form-urlencoded.

If you are not permitted to perform the reindex, Vonk will return statuscode 403.

Re-index Configuration

Vonk will not re-index the resources in the database all at once, but in batches. The re-index operation will process all batches until all resources are re-indexed. You can control the size of the batches in the Vonk settings.

"ReindexOptions": {
    "BatchSize": 100

Use any integer value >= 1.


Every search parameter has to have either:

  • a valid FhirPath in it’s Expression property, or
  • be a Composite search parameter and specify at least one component.