6.9    Phonetic Search Parameters
  • FHIR Storage
  • 6.0 Concepts in Smile CDR
  • 6.1 FHIR Storage Modules
  • 6.2 FHIR Endpoint Module
  • 6.3 FHIRWeb Console
  • 6.4 OpenAPI / Swagger Support
  • 6.5 FHIR Endpoint Customization
  • 6.6 Resource IDs
  • 6.7 Search Parameters
  • 6.8 Search Parameter Features
  • 6.9 Phonetic Search Parameters
  • 6.10 Search Parameter Tuning
  • 6.11 Search Parameter Reindexing
  • 6.12 Searching for Data
  • 6.13 Creating Data
  • 6.14 Reading Data
  • 6.15 Updating Data
  • 6.16 Deleting Data
  • 6.17 Binary Data
  • 6.18 Request Tracing and Provenance
  • 6.19 FHIR Versions
  • 6.20 Resource Versions and Versioned References
  • 6.21 Tags, Profiles, and Security Labels
  • 6.22 Partitioning and Multitenancy
  • 6.23 Custom Resource Types
  • 6.24 Batch and Scheduled Jobs
    • 6.11    Search Parameter Reindexing   
       Table of Contents

    Search Parameter Tuning

    6.10.1Search Parameter Initialization

     

    The FHIR specification describes a rich set of default Search Parameters for every resource type, and these are all enabled by default. Every enabled search parameter means additional processing work when a resource is written, so disabling search parameters that are not used can have a significant impact on write performance.

    For example, out of the box, every time a Patient resource is written, distinct search parameters are created to index:

    • The family name
    • The given name
    • All names as a single index
    • Email address
    • Phone number
    • All identifers
    • All street address lines
    • All listed address cities
    • All listed address states/provinces
    • All listed address countries
    • All listed address postal/zip codes
    • Gender

    Having all of the indexes above can be useful if you are trying to build a general-purpose system that will support searching by any combination of a wide range of demographics.

    On the other hand, if you are implementing one or more Implementation Guides that only mandate support for a specific limited number of search parameters, indexing all of these fields adds processing time and index disk space every time a resource is written.

    The performance and storage space difference can be dramatic when you disable unnecessary search parameters. Tuning is highly recommended.

    6.10.2Checking Active Parameters

     

    Search Parameters are controlled in your repository using SearchParameter resources. A simple search can be used to determine which search parameters are active, e.g.:

    https://try.smilecdr.com/baseR4/SearchParameter?base=Patient&status=active

    You can disable unwanted Search Parameters by updating these resources and setting the status to retired.

    6.10.3Seeding Search Parameters

     

    By default, the system will automatically initalize your repository with all Search Parameters defined in the base FHIR specification when you create a new FHIR repository.

    If you wish to automatically adjust this seeding, you can do this using the Search Parameter Seeding settings. Note that it is fine to adjust these after the repository has been created, even if the default set of search parameters has already been created.

    6.10.3.1Patterns

    Patterns for both enabling and disabling search parameters take the forms:

    • [resourceType]:[paramName] (One specific search parameter for one resource type) – e.g. "Practitioner:name"
    • *:[paramName] (any search parameters with the given name across all resource types) – e.g. "*:name"
    • [resourceType]:* (all search parameters for the given resource type) – e.g. "Practitioner:*"
    • * (all search parameters for all resource types)

    Multiple patterns may be specified using either a newline or a comma to separate the values.

    Enable patterns take precedence over disable patterns, so for example if you specify a disable pattern of Patient:* and an enable pattern of Patient:name, Patient.identifier then all search parameters for the Patient resource will be disabled except for name and identifier.

    Note that there are a small number of search parameters that can not be disabled as they are required for routine operation of the CDR. These include *:url (used by various parts of the validator and terminollogy services) and Subscription:* (used by the Subscription module). The system will not permit these to be disabled and will automatically ignore any attempts to disable them through disable patterns.

    6.10.3.2Example

    The following example shows seeding settings appropriate for a repository being used to support the CARIN Consumer Directed Payer Data Exchange (CARIN IG for Blue Button®) Implementation Guide.

    6.10.3.2.1Disable Patterns

    Patient:*
Practitioner:*
ExplanationOfBenefit:*
Coverage:*
Organization:*

    6.10.3.2.2Enable Patterns

    Patient:identifier
Coverage:identifier
ExplanationOfBenefit:identifier
ExplanationOfBenefit:patient
ExplanationOfBenefit:type
ExplanationOfBenefit:service-date
ExplanationOfBenefit:claim
ExplanationOfBenefit:coverage
ExplanationOfBenefit:encounter
ExplanationOfBenefit:enterer
ExplanationOfBenefit:facility
ExplanationOfBenefit:provider
ExplanationOfBenefit:payee
       6.9    Phonetic Search Parameters
  • FHIR Storage
  • 6.0 Concepts in Smile CDR
  • 6.1 FHIR Storage Modules
  • 6.2 FHIR Endpoint Module
  • 6.3 FHIRWeb Console
  • 6.4 OpenAPI / Swagger Support
  • 6.5 FHIR Endpoint Customization
  • 6.6 Resource IDs
  • 6.7 Search Parameters
  • 6.8 Search Parameter Features
  • 6.9 Phonetic Search Parameters
  • 6.10 Search Parameter Tuning
  • 6.11 Search Parameter Reindexing
  • 6.12 Searching for Data
  • 6.13 Creating Data
  • 6.14 Reading Data
  • 6.15 Updating Data
  • 6.16 Deleting Data
  • 6.17 Binary Data
  • 6.18 Request Tracing and Provenance
  • 6.19 FHIR Versions
  • 6.20 Resource Versions and Versioned References
  • 6.21 Tags, Profiles, and Security Labels
  • 6.22 Partitioning and Multitenancy
  • 6.23 Custom Resource Types
  • 6.24 Batch and Scheduled Jobs
    • 6.11    Search Parameter Reindexing