An important concept for setting up a FHIR repository is defining the search parameters that will be indexed and made available for searching by the system.
Search parameters are essentially named paths within resources that are indexed by the system so that they can be used to find resources that match a given criteria.
For example, the FHIR specification defines the gender search parameter on the Patient resource, giving it a path of Patient.gender. This means that every time a new Patient resource is created – or an existing one is updated – the value found at the path Patient.gender will be indexed. Clients may then use a URL search parameter named gender to find resources with a given gender.
Once these parameters have been defined in your database, clients can use them to find matching resources:
GET [base]/Patient?gender=male
The FHIR specification defines a set of built-in parameters that are wide ranging and broadly useful. For example, the FHIR definition for the Patient resource contains search parameters such as:
name (Search for patient by name)birthdate (Search for patient by date of birth)identifier (Search for patient by identifier)For a general purpose repository, using the default search parameters is useful since these parameters represent a wide variety of use cases. Additionally, using the default parameters is good for interoperability since clients may expect standard parameters to be supported across different servers.
However, it is often useful to customize the supported search parameters. For example:
In a relational FHIR Storage module, each search parameter is represented by a SearchParameter resource in the database. When Smile CDR starts for the first time, the database will be preseeded with search parameter resources that correspond to the various default parameters.
If you want to customize the available search parameters, there are several ways to do so.
This functionality has been removed as of 2022.02.R01.
A new search parameter can also be created by simply uploading an appropriate SearchParameter resource. This is same process used to upload any other type of resource.
For example, POSTing the following resource to a server that supports custom search parameters will create a new search parameter on the Patient resource named eyecolour.
{
"resourceType": "SearchParameter",
"title": "Eye Colour",
"base": [ "Patient" ],
"status": "active",
"code": "eyecolour",
"type": "token",
"expression": "Patient.extension('http://acme.org/eyecolour')",
"xpathUsage": "normal"
}
Smile CDR gathers statistics at runtime about the actual values indexed by a search parameter for resources in the database and the use of that search parameter by clients.
The following statistics are gathered:
Patient.gender) will have a low value spread. A parameter that can contain many different values (e.g. Observation.value) could have a much higher value spread.Smile CDR can be configured to enable the FHIR _filter search parameter, using the filter_search.enabled property.
The filter search parameter is extremely powerful, as it allows a level of expressiveness in searches that is not possible with standard REST URL search parameters. It also potentially allows clients to perform searches for which no appropriate database indexes exist, making it a potentially dangerous operation for public servers. As such it is disabled by default.
Users of the Filter Search Parameter are advised to examine the generated SQL (e.g. by enabling Performance Tracing and then examining the Transaction Log) and ensuring that the database has indexes to appropriately support the queries being performed.
It is possible to trigger a manual reindexing of data in the repository. This is generally done for one of the following reasons:
In cases where Search Parameters have been changed in some way and the Mark Resources for Reindexing After SearchParameter Change property is not enabled, a reindex may be required in order to force data that was created prior to SearchParameter changes to be indexed. This setting is disabled by default. When reindexing because of a SearchParameter change, it is a good idea to include the type parameter shown below.
If Enforce Referential Integrity on Write is not enabled, it is possible to create resources with references that are not valid at the time that the resource is created. In that case, the reference will not be indexed even if the target resource is later created. A manual reindex is then required in order to correct this.
The $reindex operation has similar syntax to the $delete-expunge operation and offers more fine-grained control over the reindex operation over the legacy $mark-all-resources-for-reindexing operation. The $reindex operation can be called in one of two ways, either with a list of urls to be reindexed or with everything=true. If everything=true then the urls parameter is ignored and all resources will be reindexed. Otherwise, only the resources matching the urls are reindexed.
everything and batchSize. Reindex everything is now automatically assumed if no URLs are supplied, and the batch size is now automatically set.
urls – (optional) If supplied, an ordered list of resource search urls to be reindexed. See Reindex URLs below for more information.The reindex operation uses search URLs to identify resources that should be reindexed. A search URL takes the form {resourceType}?[optional search parameters]. It does not include the base part of the URL.
For example, the following URL indicates that all resources of type Patient should be reindexed: Patient?
The following URL indicates that all Vital Signs Observations should be reindexed. Observation?category=http://terminology.hl7.org/CodeSystem/observation-category%7Cvital-signs
If no URLs are included, than all resources of all types will be reindexed. This is not currently supported on MongoDB.
It is important to remember that the search URL applies to resources as they are currently indexed. In other words, if you have just added a new search parameter to your repository and have not yet reindexed your data, you should not use that search parameter in your reindex URL since no resources will actually match it yet (so the reindex will not find and reindex any resources at all).
To reindex a specific set of URLs in order, call:
POST /$reindex
Content-Type: application/fhir+json
{
"resourceType": "Parameters",
"parameter": [ {
"name": "url",
"valueString": "Patient?active=true"
}, {
"name": "url",
"valueString": "Observation?subject.active=true"
} ]
}
To reindex all Practitioner and all Patient resources, call:
POST /$reindex
Content-Type: application/fhir+json
{
"resourceType": "Parameters",
"parameter": [ {
"name": "url",
"valueString": "Practitioner?"
}, {
"name": "url",
"valueString": "Patient?"
} ]
}
To reindex all resources, simply call the $reindex operation with no parameters.
POST /$reindex
The $reindex operation creates a batch job that can be stopped and restarted on the Batch Job Management page.
The $reindex operation is partition aware. The operation is performed only on the partition that was included in the request and the job is only started if the user is allowed to access that partition. In order to perform a $reindex everything=true, the user must have access to all resource types on that partition.
The following documentation is provided for the old reindexing operation. Users are encouraged to use the new operation as it provides better control of what's indexed and a user-interface to view, stop, and restart the reindexing job.
The following arguments are supported for this operation:
type – (optional) If supplied, specifies the specific resource type to reindex. If not specified, all resource types will be reindexed.To perform a manual reindex, the following operation can be invoked at the server (root) level of the FHIR Endpoint module (i.e. the base URL of the FHIR endpoint). To specifiy parameters, a resource of type Parameters must be included as the body of a POST request. See the following examples for more details.
-- DEPRECATED --
GET /$mark-all-resources-for-reindexing
POST /$mark-all-resources-for-reindexing
Content-Type: application/fhir+json
{
"resourceType": "Parameters",
"parameter": [ {
"name": "type",
"valueString": "Patient"
} ]
}