The FHIR Validation Services configuration category includes the following configurable options:
Concurrent Bundle Validation Thread Count
Concurrent Bundle Validation
Remote Terminology Service: Base URL
Terminology Basic Auth Password
Terminology Basic Auth Username
Remote Terminology Service: Enabled
Remote Terminology Service: Log HTTP Calls
Accept All Codings Only
Code Display Mismatch Policy
Local Reference Policy
Skip Contained Resource Validation
Suppress Validation Message Patterns
Unknown CodeSystem Validation Policy
|
|
Concurrent Bundle Validation Thread Count |
|
|
|
| POSITIVE_INTEGER | |
| This value is only used when Concurrent Bundle Validation property is enabled. It specifies the number of threads allocated to validating bundle resources. | |
|
|
4
|
|
|
|
|
Concurrent Bundle Validation |
|
|
|
| BOOLEAN | |
| If this is enabled, bundle resources will be validated in parallel threads. The number of threads is determined by the value of Concurrent Bundle Validation Thread Count property. Note that enabling this feature means bundle structure itself is not validated, only the resources within it are validated. | |
|
|
false
|
|
|
|
|
Remote Terminology Service: Base URL |
|
|
|
| STRING | |
| The Base URL for the FHIR server containing terminology services to use for validation. | |
|
|
| (no default) | |
|
|
|
Terminology Basic Auth Password |
|
|
|
| PASSWORD | |
| Password used for the basic auth of the Remote Terminology Service | |
|
|
| (no default) | |
|
|
|
Terminology Basic Auth Username |
|
|
|
| STRING | |
| Username used for the basic auth of the Remote Terminology Service | |
|
|
| (no default) | |
|
|
|
Remote Terminology Service: Enabled |
|
|
|
| BOOLEAN | |
| If enabled, a FHIR REST-based terminology service will be used for validation. See Remote Terminology Services for more information on this feature. | |
|
|
false
|
|
|
|
|
Remote Terminology Service: Log HTTP Calls |
|
|
|
| BOOLEAN | |
| If enabled, debugging HTTP logs for outbound terminology service calls will be added to smile.log. Note that this logging is very verbose and should only be used for troubleshooting. | |
|
|
false
|
|
|
|
|
Accept All Codings Only |
|
|
|
| BOOLEAN | |
| This setting enables the custom AND logic for multiple Coding validation, as opposed to the logical OR logic that is enabled by default. All codings must validate as OK as opposed to just a single one if this is enabled. | |
|
|
false
|
|
|
|
|
Code Display Mismatch Policy |
|
|
|
| ENUM | |
| Values |
|
| This setting determines how the validator should behave if the display name for a Coding being validated does not agree with the expected display name from the CodeSystem. See Code Display Mismatch Policy for more information. | |
|
|
WARNING
|
|
|
|
|
Local Reference Policy |
|
|
|
| ENUM | |
| Values |
|
| This property controls whether the validator should attempt to dereference/load resource references from the resource being validated to ensure that they exist, and are valid for the given reference. This type of validation is more thorough but also increases the time that an individual resource validation will take. See Validating References for more information. | |
|
|
NOT_VALIDATED
|
|
|
|
|
Skip Contained Resource Validation |
|
|
|
| BOOLEAN | |
| This setting disables the validation of contained resources. | |
|
|
false
|
|
|
|
|
Suppress Validation Message Patterns |
|
|
|
| STRING_MULTILINE | |
| This option can be used to specify regex patterns (one per line) for suppressing validation messages. See Suppressing Validation Messages for more information. | |
|
|
| (no default) | |
|
|
|
Unknown CodeSystem Validation Policy |
|
|
|
| ENUM | |
| Values |
|
| This setting controls how the validator will behave when a Coding contains a CodeSystem reference (Coding.system) that can not be resolved. See Handling Missing CodeSystems for more information. | |
|
|
GENERATE_ERROR
|
|
|