[CORE-273] SHRINEACT queries with date constraints are losing the constraints on i2b2ACT side - i2b2 JIRA

Details

Type: Bug
Status: Closed
Priority: Major
Resolution: Fixed
Affects Version/s: None
Fix Version/s: 1.7.09c
Component/s: None
Labels:
None

Affects View/s:

Query Tool
i2b2 Feature/s:

Constraints - Date

Affects Web Browser/s:

All Web Browsers

Description

Create any query on SHRINEACT and put some date constraints on any of the concepts. Execute the query and let it finish. Access the same query from i2b2 local webclient, the date constraint does not show up. On the database side, the SQL created for the SHRINE query saves the constraint, but the xml in the QT_Query_Master table does not save it resulting in this issue.

Attachments

Activity

Ascending order - Click to sort in descending order

Nich added a comment - 14/Aug/17 11:50 AM

The SHRINE is sending DATE and not DATETIME in the XML. If a date constraint is in the form of a date and not datetime, the generated SQL is fine (and automatically makes it a datetime in the SQL), but the XML saved is blank. This affects both date constraints set at the <panel> level (the old way) and date constraints set at the <item> level (the new way & workbench way).

For example, here are two problematic request messages:

                <panel>
                    <panel_number>1</panel_number>
                    <panel_timing>ANY</panel_timing>
                    <panel_accuracy_scale>100</panel_accuracy_scale>
                    <panel_date_from>2016-12-01</panel_date_from>
                    <panel_date_to>2017-08-14</panel_date_to>
                    <invert>0</invert>
                    <total_item_occurrences>1</total_item_occurrences>
                    <item>
                        <hlevel>2</hlevel>
                        <item_name>Circulatory system</item_name>
                        <item_key>\\i2b2metadata\i2b2metadata\Diagnosis\Circulatory system (390-459)\</item_key>
                        <item_icon>FA</item_icon>
                        <tooltip>Diagnoses \ Circulatory system</tooltip>
                        <class>ENC</class>
                        <item_is_synonym>false</item_is_synonym>
                    </item>
                </panel>

                <panel>
                    <panel_number>1</panel_number>
                    <panel_timing>ANY</panel_timing>
                    <panel_accuracy_scale>100</panel_accuracy_scale>
                    <invert>0</invert>
                    <total_item_occurrences>1</total_item_occurrences>
                    <item>
                        <hlevel>2</hlevel>
                        <item_name>Circulatory system</item_name>
                        <item_key>\\i2b2metadata\i2b2metadata\Diagnosis\Circulatory system (390-459)\</item_key>
                        <item_icon>FA</item_icon>
                        <tooltip>Diagnoses \ Circulatory system</tooltip>
                        <class>ENC</class>
                        <item_is_synonym>false</item_is_synonym>
                        <constrain_by_date>
                            <date_from>2016-12-01</date_from>
                            <date_to>2017-08-14</date_to>
                        </constrain_by_date>
                    </item>
                </panel>

Nich added a comment - 14/Aug/17 11:50 AM The SHRINE is sending DATE and not DATETIME in the XML. If a date constraint is in the form of a date and not datetime, the generated SQL is fine (and automatically makes it a datetime in the SQL), but the XML saved is blank. This affects both date constraints set at the <panel> level (the old way) and date constraints set at the <item> level (the new way & workbench way). For example, here are two problematic request messages: <panel> <panel_number>1</panel_number> <panel_timing>ANY</panel_timing> <panel_accuracy_scale>100</panel_accuracy_scale> <panel_date_from>2016-12-01</panel_date_from> <panel_date_to>2017-08-14</panel_date_to> <invert>0</invert> <total_item_occurrences>1</total_item_occurrences> <item> <hlevel>2</hlevel> <item_name>Circulatory system</item_name> <item_key>\\i2b2metadata\i2b2metadata\Diagnosis\Circulatory system (390-459)\</item_key> <item_icon>FA</item_icon> <tooltip>Diagnoses \ Circulatory system</tooltip> <class>ENC</class> <item_is_synonym>false</item_is_synonym> </item> </panel> <panel> <panel_number>1</panel_number> <panel_timing>ANY</panel_timing> <panel_accuracy_scale>100</panel_accuracy_scale> <invert>0</invert> <total_item_occurrences>1</total_item_occurrences> <item> <hlevel>2</hlevel> <item_name>Circulatory system</item_name> <item_key>\\i2b2metadata\i2b2metadata\Diagnosis\Circulatory system (390-459)\</item_key> <item_icon>FA</item_icon> <tooltip>Diagnoses \ Circulatory system</tooltip> <class>ENC</class> <item_is_synonym>false</item_is_synonym> <constrain_by_date> <date_from>2016-12-01</date_from> <date_to>2017-08-14</date_to> </constrain_by_date> </item> </panel>

Janice Donahoe added a comment - 22/Nov/17 11:18 AM

2017-Nov-22
Tested with the latest build and the dates are not being carried forward to the local client when they are added within the SHRINE client.

Janice Donahoe added a comment - 22/Nov/17 11:18 AM 2017-Nov-22 Tested with the latest build and the dates are not being carried forward to the local client when they are added within the SHRINE client.

Janice Donahoe added a comment - 07/Dec/17 1:27 PM

Mike tested this again with the latest changes and he said it is now working correctly. It was testing in a SHRINE environment.

Janice Donahoe added a comment - 07/Dec/17 1:27 PM Mike tested this again with the latest changes and he said it is now working correctly. It was testing in a SHRINE environment.

i2b2 Core Software

SHRINEACT queries with date constraints are losing the constraints on i2b2ACT side

Details

Description

Attachments

Activity

People

Dates