The CQL configuration category includes the following configurable options:
Data Analysis
Collapse Data Analysis
CQL Language Level
Default Model Info
Disable List Demotion
Disable List Promotion
Disable List Traversal
Disable Method Invocation
Annotations
Date Range Optimization
Detailed Errors
Enable Interval Demotion
Enable Interval Promotion
Locators
Results Type
Error Level
Require From Keyword
Signature Level
Format for ELM
Validate units
Semantic Analysis
Profile Mode
Search Filter Mode
Terminology Filter Mode
Debug Logging
Enable Expression Caching
Enable Validation
ValueSet Code Lookup Mode
ValueSet Expansion Mode
ValueSet Membership Mode
ValueSet Pre-Expansion Mode
Use Embedded Libraries
|
|
Data Analysis |
|
|
|
| BOOLEAN | |
| Determines whether the CQL compiler should do detailed data-requirements analysis when compiling CQL. | |
|
|
false
|
|
|
|
|
Collapse Data Analysis |
|
|
|
| BOOLEAN | |
| Determines whether the CQL compiler should "collapse" (i.e. optimize) data-requirements when they are generated. | |
|
|
false
|
|
|
|
|
CQL Language Level |
|
|
|
| STRING | |
| This setting controls the language-level that the CQL compiler should run in. Most DSTU3 content uses CQL version 1.3, while newer content uses CQL version 1.5. If you experience compilation errors please verify the CQL language level being used in the expressions. | |
|
|
1.5
|
|
|
|
|
Default Model Info |
|
|
|
| BOOLEAN | |
| Indicates to include default model information. | |
|
|
false
|
|
|
|
|
Disable List Demotion |
|
|
|
| BOOLEAN | |
| Disables demotion of list-valued expressions to singletons. | |
|
|
false
|
|
|
|
|
Disable List Promotion |
|
|
|
| BOOLEAN | |
| Disables promotion of singletons to list-valued expressions. | |
|
|
false
|
|
|
|
|
Disable List Traversal |
|
|
|
| BOOLEAN | |
| Disables traversal of paths on list-valued expressions. | |
|
|
false
|
|
|
|
|
Disable Method Invocation |
|
|
|
| BOOLEAN | |
| Disables method-style invocation support. | |
|
|
false
|
|
|
|
|
Annotations |
|
|
|
| BOOLEAN | |
| Indicates that the translator should produce source code annotations as part of the output. | |
|
|
false
|
|
|
|
|
Date Range Optimization |
|
|
|
| BOOLEAN | |
| Indicates that the translator should perform date range optimization of retrieves where possible. | |
|
|
false
|
|
|
|
|
Detailed Errors |
|
|
|
| BOOLEAN | |
| Indicates that the translator should produce detailed errors. | |
|
|
false
|
|
|
|
|
Enable Interval Demotion |
|
|
|
| BOOLEAN | |
| Enables demotion of interval-valued expressions to points. | |
|
|
false
|
|
|
|
|
Enable Interval Promotion |
|
|
|
| BOOLEAN | |
| Enables promotion of point-valued expressions to intervals. | |
|
|
false
|
|
|
|
|
Locators |
|
|
|
| BOOLEAN | |
| Indicates that the translator should include source code locators within output ELM. | |
|
|
false
|
|
|
|
|
Results Type |
|
|
|
| BOOLEAN | |
| Indicates that the translator should include result types in the output ELM. | |
|
|
false
|
|
|
|
|
Error Level |
|
|
|
| ENUM | |
| Values |
|
| Determines the level of severity required for the CQL compiler to report an issue. Info enables all messages, while Error enables only Error messages | |
|
|
Info
|
|
|
|
|
Require From Keyword |
|
|
|
| BOOLEAN | |
| Indicates that all queries will be required to start with a from keyword. | |
|
|
false
|
|
|
|
|
Signature Level |
|
|
|
| ENUM | |
| Values |
|
| Determines the level of detail to output to compiled CQL for signature resolution. This should generally not be changed. | |
|
|
All
|
|
|
|
|
Format for ELM |
|
|
|
| ENUM | |
| Values |
|
| The target format for the output | |
|
|
JSON
|
|
|
|
|
Validate units |
|
|
|
| BOOLEAN | |
| This flag controls whether the CQL compiler validates unit quantities for conversion | |
|
|
true
|
|
|
|
|
Semantic Analysis |
|
|
|
| BOOLEAN | |
| This flag controls whether the CQL compiler should emit compiled CQL or simply run semantic analysis. | |
|
|
false
|
|
|
|
|
Profile Mode |
|
|
|
| ENUM | |
| Values |
|
| Profiles are completely unsupported for now, default to OFF until supported. Options: ENFORCED, OPTIONAL, DECLARED, TRUST, OFF | |
|
|
OFF
|
|
|
|
|
Search Filter Mode |
|
|
|
| ENUM | |
| Values |
|
| Applies to all search parameters, EXCEPT terminology search parameters, which are controlled by terminology settings. Options: AUTO, USE_SEARCH_PARAMETERS, FILTER_IN_MEMORY | |
|
|
USE_SEARCH_PARAMETERS
|
|
|
|
|
Terminology Filter Mode |
|
|
|
| ENUM | |
| Values |
|
| How to do a filter, if and when we need a filter. e.g. Observation O where O.code ~ "ValueSet". Options: AUTO, USE_VALUE_SET_URL, USE_INLINE_CODES, FILTER_IN_MEMORY | |
|
|
FILTER_IN_MEMORY
|
|
|
|
|
Debug Logging |
|
|
|
| BOOLEAN | |
| Enabling debug logging will cause the SmileCDR server to output detailed evaluation logs for CQL. This can be useful for debug purposes. Debug logging has a significant performance impact. | |
|
|
false
|
|
|
|
|
Enable Expression Caching |
|
|
|
| BOOLEAN | |
| Enable expression caching allows to CQL engine to optimize expression reuse during evaluation, improving performance. | |
|
|
true
|
|
|
|
|
Enable Validation |
|
|
|
| BOOLEAN | |
| Enable validation checks compiled CQL prior to execution. | |
|
|
false
|
|
|
|
|
ValueSet Code Lookup Mode |
|
|
|
| ENUM | |
| Values |
|
| How to do Code Lookups. Options: AUTO, USE_VALIDATE_CODE_OPERATION, USE_CODESYSTEM_URL | |
|
|
USE_CODESYSTEM_URL
|
|
|
|
|
ValueSet Expansion Mode |
|
|
|
| ENUM | |
| Values |
|
| How to do Expansions. Options: AUTO, USE_EXPAND_OPERATION, PERFORM_NAIVE_EXPANSION | |
|
|
PERFORM_NAIVE_EXPANSION
|
|
|
|
|
ValueSet Membership Mode |
|
|
|
| ENUM | |
| Values |
|
| How to do ValueSet Code MemberShip. Options: AUTO, USE_VALIDATE_CODE_OPERATION, USE_EXPANSION | |
|
|
USE_EXPANSION
|
|
|
|
|
ValueSet Pre-Expansion Mode |
|
|
|
| ENUM | |
| Values |
|
| How to treat pre-expanded value sets. If a value set is not pre-expanded, fall back to the expansion behavior. Defined by the expansion Mode. Options: REQUIRE, USE_IF_PRESENT, IGNORE | |
|
|
USE_IF_PRESENT
|
|
|
|
|
Use Embedded Libraries |
|
|
|
| BOOLEAN | |
| SmileCDR ships with embedded versions of some commonly used CQL libraries, specifically FHIRHelpers. This switch determines whether or not the cql engine will use those embedded libraries.In the case you want to supply your our version of FHIRHelpers, you should set this to false | |
|
|
true
|
|
|