Skip to main content

         This documentation site is for previous versions. Visit our new documentation site for current releases.      

Using Elasticsearch

Updated on April 23, 2021

To use Elastic search, call the D_<CodeSetName> data page as your data source for either an auto-complete control or elsewhere in any other search field.

The above data page takes two parameters:

  • Code – Data string to search for
  • CodeSetType – Name of the code set that you want to search on

For all classes, you can perform the search for code and description (respective fields for HCPCS, CPT® and so on). It is defined through a search model that is a pySearch rule of type Custom search properties created in each of the classes, which instructs the Elastic code the fields to enable for search.

Note: Although not advisable, but if more fields for search are required, they can be added to the pySearch and adequate data indexing is done. Note that adding too much data may significantly increase the Elastic index file causing potentially poor performance.

The data source for the data page is the Activity named PrepareQueryString which prepares the query to be passed and calls the report definition. This Activity sets the properties based on the parameter that is passed and then calls the report definition rule by passing the query string to fetch the records for the specified code set type.

  • Previous topic Step 10: Implementing Elasticsearch on code sets
  • Next topic Step 11: Implementing Elasticsearch on sample data objects

Have a question? Get answers now.

Visit the Support Center to ask questions, engage in discussions, share ideas, and help others.

Did you find this content helpful?

Want to help us improve this content?

We'd prefer it if you saw us at our best. is not optimized for Internet Explorer. For the optimal experience, please use:

Close Deprecation Notice
Contact us