Measure Evaluation
The Measure Evaluation configuration category includes the following configurable options:
Apply Scoring
Subject Chunk Size
Measure Chunk Size
Measure Report default reporter
S3 Bucket Name
S3 Endpoint
S3 Access Key
S3 Region
S3 Secret Key
S3 Subject CQL Results with Evaluated Resources
S3 Subject CQL Results
Threaded Subject Chunk Size
Number of Threads
Enabled Threading
Measure Report Reporter from Group
Include Patients from Related Managing Organizations
|
|
Apply Scoring |
|
|
|
| BOOLEAN | |
| Applies a scoring algorithm during measure evaluation. | |
|
|
true
|
|
|
|
|
Subject Chunk Size |
|
|
|
| NON_NEGATIVE_INTEGER | |
| The maximum quantity of subjects to process per batch2 job work-chunk. This allows for batch2 job work-chunks to optimally process a maximum volume of subjects in parallel, setting this value too high will maximize work-chunk throughput, but will slow processing speed. | |
|
|
50
|
|
|
|
|
Measure Chunk Size |
|
|
|
| NON_NEGATIVE_INTEGER | |
| The maximum quantity of measures that will be evaluated per batch2 job work-chunk during distributed measure evaluation request. This allows for batch2 job work-chunks to optimally process at a specific volume, setting this value too high will maximize work-chunk throughput, but slow processing speed. Example: If requesting 9 Measure resources to be evaluated, and 'Measure Chunk Size'= 4, it will create 3 Measure-Chunks: 1) Measures 1, 2, 3, 4. 2) Measures 5, 6, 7, 8. 3) Measure 9 | |
|
|
4
|
|
|
|
|
Measure Report default reporter |
|
|
|
| STRING | |
| The default value that will be added to MeasureReport.reporter field when executing Async $evaluate-measure operation. This should be a reference to Organization resource. | |
|
|
| (no default) | |
|
|
|
S3 Bucket Name |
|
|
|
| STRING | |
| The AWS S3 bucket where Evaluation Type 'subject' results will be saved in distributed (batch2) mode. The Bucket must be created before referenced in configuration. | |
|
|
| (no default) | |
|
|
|
S3 Endpoint |
|
|
|
| STRING | |
| S3 Endpoint is primarily used for local s3 server override of aws default endpoints. This is mainly used for testing purposes, standard use would rely on common aws endpoint for region (e.g., s3.us-east-1.amazonaws.com). | |
|
|
| (no default) | |
|
|
|
S3 Access Key |
|
|
|
| STRING | |
| The S3 Access Key used to provide access to named S3 bucket. Recommend setting this value through environment variable to avoid exposing | |
|
|
| (no default) | |
|
|
|
S3 Region |
|
|
|
| STRING | |
| The S3 region code for where the S3 bucket is located. Example value: 'us-east-1' | |
|
|
us-east-1
|
|
|
|
|
S3 Secret Key |
|
|
|
| STRING | |
| The S3 Secret used to provide access to named S3 bucket. Recommend setting this value through environment variable to avoid exposing | |
|
|
| (no default) | |
|
|
|
S3 Subject CQL Results with Evaluated Resources |
|
|
|
| BOOLEAN | |
| Show CQL Resources used to evaluate each Cql expression with CQL results. This functionality is for distributed (batch2) mode only. This feature requires S3 configurations. | |
|
|
false
|
|
|
|
|
S3 Subject CQL Results |
|
|
|
| BOOLEAN | |
| CQL Expression results will be saved to S3 instead of producing FHIR Measure Report. This functionality is for distributed (batch2) mode only. This feature requires S3 configurations. | |
|
|
false
|
|
|
|
|
Threaded Subject Chunk Size |
|
|
|
| NON_NEGATIVE_INTEGER | |
| The number of patients to batch per thread for parallel processing of data for measure evaluation. Example: If processing 1000 patients in a measure evaluation query, thread-Number =2, and Thread-Batch-Size is set to 500, then system will split 1000 patients into two batches of 500 patients, distribute query to two threads for processing, and collect results from threads when complete. | |
|
|
25
|
|
|
|
|
Number of Threads |
|
|
|
| NON_NEGATIVE_INTEGER | |
| The quantity of concurrent processors to make available from the system for measure evaluation operations & $care-gaps queries. Note: This value needs to be less than available processors on SmileCdr instance to perform optimally. | |
|
|
2
|
|
|
|
|
Enabled Threading |
|
|
|
| BOOLEAN | |
| Enabling Threading will allow for additional parallel processing of measure evaluation of subject quantity up to the setting 'Threaded Batch Size'. | |
|
|
false
|
|
|
|
|
Measure Report Reporter from Group |
|
|
|
| BOOLEAN | |
| If set to true, evaluate-measure operation will attempt to source MeasureReport.reporter from evaluate-measure operation's 'subject' or 'practitioner' parameter by using the Group's resource field, managingEntity. If unable to source reference from Group, MeasureReport reporter will use default dqm.evaluate_measure.reporter setting. | |
|
|
true
|
|
|
|
|
Include Patients from Related Managing Organizations |
|
|
|
| BOOLEAN | |
| If set to true, evaluate-measure subject parameter will collect Patient resources with a matching Patient.managingOrganization reference in addition to Organizations related by the Organization.partOf field. | |
|
|
false
|
|
|
You are about to leave the Smile Digital Health documentation and navigate to the Open Source HAPI-FHIR Documentation.