The DQM configuration category includes the following configurable options:
Chunk Size
Cql detail data analysis
Cql optimal data analysis
Cql Engine version
Cql Engine level to report issue
Cql data analysis for signature resoltion
Cql Engine flag to validate units
Cql Engine option to emit compiled or semantic analysis
Cql debug logging
Cql Engine runtime options
Use Embedded Libraries
|
Chunk Size |
|
|
NON_NEGATIVE_INTEGER | |
Number of Subjects per chunk during evaluation | |
|
|
1000
|
|
|
|
Cql detail data analysis |
|
|
BOOLEAN | |
Determines whether the CQL compiler should do detailed data-requirements analysis when compiling CQL. | |
|
|
false
|
|
|
|
Cql optimal data analysis |
|
|
BOOLEAN | |
Determines whether the CQL compiler should "collapse" (i.e. optimize) data-requirements when they are generated. | |
|
|
false
|
|
|
|
Cql Engine version |
|
|
STRING | |
This setting controls the language-level that the CQL compiler should run in. Most DSTU3 content in the wild uses CQL version 1.3, while newer content uses CQL version 1.5. If you experience compilation errors with some content you can try setting a different compatibility level to see if they are resolved. | |
|
|
1.5
|
|
|
|
Cql Engine level to report issue |
|
|
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
|
|
|
|
Cql data analysis for signature resoltion |
|
|
ENUM | |
Values |
|
Determines the level of detail to output to compiled CQL for signature resolution. This should generally not be changed. | |
|
|
None
|
|
|
|
Cql Engine flag to validate units |
|
|
BOOLEAN | |
This flag controls whether the CQL compiler validates unit quantities for conversion | |
|
|
true
|
|
|
|
Cql Engine option to emit compiled or semantic analysis |
|
|
BOOLEAN | |
This flag controls whether the CQL compiler should emit compiled CQL or simply run semantic analysis. This should never be set to true | |
|
|
false
|
|
|
|
Cql debug logging |
|
|
BOOLEAN | |
Enabling debug logging will cause the HAPI server to output detailed evaluation logs for CQL. This can be useful for debug purposes. Debug logging has a significant performance impact. | |
|
|
false
|
|
|
|
Cql Engine runtime options |
|
|
ENUM | |
Values |
|
This option is a list of flags for the CQL engine. EnableValidation checks compiled CQL prior to execution. EnableExpressionCaching allows to CQL engine to optimize expression reuse during evaluation, improving performance. | |
|
|
EnableExpressionCaching
|
|
|
|
Use Embedded Libraries |
|
|
BOOLEAN | |
HAPI 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
|
|
|