|
Priority
|
No.
|
Type
|
Summary
|
Description
|
|
2 - High
|
6639
|
Change/Defect
|
Visio file will not compile arrows as line ends
|
Visio file will not compile arrows as line ends
The created visio files allows an arrow as a line end but when the file is compiled the arrow does not show up in the report. This arrow is needed for the MBMD Chronic Pain Report percentile profile.
RTS 04/07/10
|
|
2 - High
|
6666
|
Request: Enhancement
|
MMPI-2-RF: add two comparison groups
|
Add two new comparison groups: Spine Surgery/Spinal Cord Stimulator Candidate (Men) and Spine Surgery/Spinal Cord Stimulator Candidate (Women)
|
|
2 - High
|
6667
|
Change/Defect
|
MBMD Report Type conversion
|
For the 2.6 MBMD release, the two existing MBMD report types will be discontinued and replaced with 6 new report types. The existing report types are:
51941 - MBMD Interpretive Report
51942 - MBMD Profile Report
These report types will be replaced by the following 6 report types:
52050 - MBMD General Medical Profile Report
52051 - MBMD General Medical Interpretive Report
52052 - MBMD Bariatric Profile Report
52053 - MBMD Bariatric Interpretive Report
52054 - MBMD Pain Patient Profile Report
52055 - MBMD Pain Patient Interpretive Report
The decision has been made that when 2.6 Q Local is launched, the HASP will be examined, and any existing report usages for '51941 - MBMD Interpretive Report' will automatically be converted to usages for '52051 - MBMD General Medical Interpretive Report', and any existing report usages for '51942 - MBMD Profile Report' will automatically be converted to usages for '52050 - MBMD General Medical Profile Report'.
|
|
2 - High
|
6668
|
Change/Defect
|
Reprints of pre-2.6 MBMD reports
|
For the 2.6 MBMD release, the two existing MBMD report types will be discontinued and replaced with 6 new report types. The existing report types are:
51941 - MBMD Interpretive Report
51942 - MBMD Profile Report
These report types will be replaced by the following 6 report types:
52050 - MBMD General Medical Profile Report
52051 - MBMD General Medical Interpretive Report
52052 - MBMD Bariatric Profile Report
52053 - MBMD Bariatric Interpretive Report
52054 - MBMD Pain Patient Profile Report
52055 - MBMD Pain Patient Interpretive Report
It has been decided that records which have been scored and reported using the pre-2.6 report types will be handled in the following manner in 2.6 and forward:
1. Any record previously printed as an 'MBMD Profile Report' may be reprinted FOR FREE as any one of the following:
52050 - MBMD General Medical Profile Report
52052 - MBMD Bariatric Profile Report
Q Local will charge the user to print any of the other four MBMD report types.
2. Any record previously printed as an 'MBMD Interpretive Report' may be reprinted FOR FREE as any one of the following:
52050 - MBMD General Medical Profile Report
52051 - MBMD General Medical Interpretive Report
52052 - MBMD Bariatric Profile Report
52053 - MBMD Bariatric Interpretive Report
Q Local will charge the user to print either of the two remaining report types.
=================
UPDATE, 07/23/2010:
NOTE: The behavior described above is *only* applicable when re-generating reports previously generated in a pre-2.6 Q Local release and reprinted in 2.6 or later either via upgrade or via import of an old TRQ file.
For all MBMD records *initially entered* in a 2.6 or later release, the user must burn a usage for each different report type printed.
|
|
2 - High
|
6673
|
Change/Defect
|
QLocaScan and vcredist yet again
|
After the release of Q Local 2.5.7, it was discovered that we inadvertently delivered a 'modern' version of QLocalScan.exe. This means that on some systems, the OS will refuse to launch QLocalScan.exe (and thus scanning is broken) unless the vcredist patch is installed --- and sometimes, apparently, not even then.
Anyway, this track was entered so we can continue to deliver the 2.3 version of QLocalScan.exe in the 2.6 release, thus staving of the problem Microsoft created for us a bit longer.
|
|
2 - High
|
6675
|
Change/Defect
|
Scanning error for MBMD forms 51929, 51930
|
Existing MBMD scan forms 51929 and 51930 have a demographic item for indicating a norm group. The corresponding 'Demographic(Norms)' variable in the Score Computer has been removed. Thus when the import logic attempts to assign a value to the 'Demographic(Norms)' variable in the Score Computer, an error occurs.
The solution is to re-implement a 'Demographic(Norms)' variable in the Score Computer as a dummy variable, but not make it visible for either OSA or manual entry. It also will not be used in scoring, and will exist for the sole purpose of preventing the occurrence of this error.
|
|
3 - Normal
|
3929
|
Change/Defect
|
Recyle Bin needs extra field removed
|
5/08 BRL - Still an issue v2.2
The recyle bin has the assessment_id field that now shows up on the far right of the screen when you scroll over. This field is not on the assessement records screen and so should not be here either. This is supposed to be a hidden field but is not being hidden on the recycle bin.
===============
(gdb - 4/2/2010)
This is an easy fix. Just remove the public static ASSESSMENTID_COLUMN field from QAssessmentRecordsTable.java, and all other references to it in that class.
|
|
3 - Normal
|
3990
|
Change/Defect
|
Extra fields on View Batch Detail screen and Battery Details screen
|
Scanned Batches->View Batch Detail (right mouse click on scanned batch) The Assessment_id column should not be visible on the screen, it is needed for the decryption routine but the user does not need to see this column. BatchDetailsUI.java
Also two columns are showing up that didn't used to be there on the view battery screen. Assessment_id and record_id, they are needed for the decrption routine but the user does not need to see these columns. List the assessment records-> right click on an assessment that is in a battery and select View All Records in a Battery.
BatteryArsUI.java
=====================
(gdb - 04/02/2010)
This is really two separate issues; however, the View Batch Detail issue appears to already be fixed. The View All Record in Battery issue is easy to fix; simply remove the static ASSESSMENTID_COLUMN and RECORDID_COLUMN fields in BatteryARsUI$MyTableModel and the methods referencing those fields, and tweak the remaining columns a bit so they fill the available space.
|
|
3 - Normal
|
4029
|
Change/Defect
|
Assessment Record Change History: Doesn't show Delete entry when entire folder is deleted
|
5/08 BRL - Still an issue v2.2
~~~~~~~~~~~~
From Assessment Records Folder view, select a folder and delete the whole folder.
From Recycle Bin, restore all the records from the folder just deleted and look at the change history of the records.
The records will have the Restore entry, but the Delete entry will be missing.
|
|
3 - Normal
|
6201
|
Request: Enhancement
|
QuickTime is pre-selected if not available on machine, Client must be selected if QuickTime is installed - Network installations do not have instructions for unselecting Client
|
As per design if the machine Q Local is going to be installed on does not have QuickTime, the QuickTime Audio Player feature is pre-selected on installation.
As per design if the QuickTime Audio Player feature is selected the Q Local Client must be selected and is grayed to prevent users from unselecting it.
If a user wants to add any combination of Q Local Shared Database or Q Local Shared Report Counter without the Q Local Client and the system does not have QuickTime installed, the user must first unselect QuickTime to be allowed to unselect the Q Local Client.
There are no instructions or explaination that one would need to uncheck the QuickTime Audio Player feature before being allowed to uncheck the Q Local Client. For a better customer experience, we would like to see some sort of instructional dialog when the Q Local Client is selected.
|
|
3 - Normal
|
6588
|
Request: Revision
|
MBMD Chronic Pain Norms - Add to MBMD PDD
|
Add Chronic Pain Norms to MBMD on Q Local.
Add Norms to PDD
Make other appropriate norm changes to PDD
11/11/09 rts
12/15/09 - Made changes to PDD. Ready for peer review. rts
12/18/09 - PDD peer reviewed by jsb. 1 grammatical change to section 3.4.2
-------------------------
Diffed and changed to fixed status. 8/5/10/ rts
|
|
3 - Normal
|
6590
|
Request: Revision
|
MBMD Chronic Pain Norms - Add to Q Local - DCD
|
Add Chronic Pain Norms to MBMD on Q Local.
Add Norms and norm info to:
SLang
Profile
11/12/09 rts
-----------------
Added Pain Patient Reports (presurgical and nonsurgical) to SLang.
Added the following profiles:
MBMDCP_GM - Prevalence score profile for Pain Patient Interp or Profile reports (valid)
MBMDCPINV_GM - Prevalence score profile for Pain Patient Interp or Profile reports (invalid)
MBMDCP.vdx - Percentile score profile for Pain Patient Interp reports (valid)
MBMDCP_Profile.vdx - Percentile score profile for Pain Patient Profile reports (valid)
MBMDCPINV.vdx - Percentile score profile for Pain Patient Interp or Profile reports (invalid)
Unit testing complete TRQs for presurgical testing and nonsurgical testing are attached. Test plan is attached.
SLang file diffed. 8/5/10 rts
--------------
Verified in 2.6.1. Ready for peer review. 8/6/10 rts
--------------
Made changes to PDD table names and spacing per peer review. 8/13/10 rts
--------
Completed peer review of PDD and SLang. 8/20/10 jsb
|
|
3 - Normal
|
6591
|
Request: Revision
|
MBMD Chronic Pain/Bariatric Norms - Changes to UEE
|
Make changes to UEE for Chronic Pain norms and Bariatric norms changes
11/12/09 rts
-----------------
Added Form IDs 250 and 251. Removed Norms field from table in guide.doc. Updated guide.pdf.
07/29/2010 rts
----------------
Ready for peer review of UEE SDK documents by DCD - guide.doc and guide.pdf. Diffed guide.doc. 8/5/10 rts
|
|
3 - Normal
|
6592
|
Request: Revision
|
MBMD Chronic Pain Norms - Add to Q Local - SD
|
Add Chronic Pain Norms to Q Local
11/12/09 rts
|
|
3 - Normal
|
6593
|
Request: Revision
|
MBMD Chronic Pain Norms - Add Scan Defs
|
Add Chronic Pain Norms to Scandef
11/12/09 rts
Added new scandef for Spanish and English answer sheets.
English: 250 MBMD No Norms English
Spanish: 251 MBMD No Norms Spanish
Record Formats and data files attached for each scandef.
Z008 checked into Perforce.
7/27/10 rts
Made changes to scandef data order to match up with UEE format. Checked in revised scandefs. Attached new record formats and data files. Ready for peer review. 7/28/10 rts
------------
Completed Peer Review. 8/19/10 jsb
|
|
3 - Normal
|
6594
|
Request: Revision
|
MBMD Bariatric Norms Answer Sheet split - Q Local - DCD
|
MBMD Bariatric Norms Answer Sheet split - Q Local - DCD
Make norms changes for bariatric norms a/s split to:
SLang
Profile
11/12/09 rts
----------
Removed Norms demographic and replace with report types.
Changed headers and coverpages on all reports per product manager request. Document attached with wording.
Unit tested using regression data.
Diffed SLang files. Verified changes in Q Local 2.6.0. Ready for peer review. 8/5/10 rts
|
|
3 - Normal
|
6595
|
Request: Revision
|
MBMD Bariatric Norms Answer Sheet split - PDD
|
MBMD Bariatric Norms Answer Sheet split - PDD
Make norms changes for bariatric norms a/s split to:
PDD
11/12/09 rts
12/15/09 - Made changes to PDD. Ready for peer review. rts
Peer Reviewed by jsb 12/18/09. 1 grammatical change to section 3.4.2.
------------
Diffed and changed to fixed status. 8/5/10/ rts
|
|
3 - Normal
|
6596
|
Request: Revision
|
MBMD Bariatric Norms Answer Sheet Split - Add Scan Defs
|
Make changes to Scan Defs for Answer Sheet changes due to Bariatric Norms changes.
11/12/09 rts
Added new scandef for Spanish and English answer sheets.
English: 250 MBMD No Norms English
Spanish: 251 MBMD No Norms Spanish
Record Formats and data files attached for each scandef.
Z008 checked into Perforce.
7/27/10 rts
Made changes to scandef data order to match up with UEE format. Checked in revised scandefs. Attached new record formats and data files. Ready for peer review. 7/28/10 rts
------------------
Completed peer review. 8/19/10 jsb
|
|
3 - Normal
|
6597
|
Request: Enhancement
|
MMPI-A: Update test logo and trademark statements
|
MMPI and Minnesota Multiphasic Personality Inventory are now registered trademarks.
1. Update PDD
2. Update MMPI-A.png
3. Update SLang (cover page, headers, and footers)
4. Update CopyrightNotice.html (View Copyright Notices) Need to also add update MMPI-2-RF TM info (TT #6552)--Karen can implement
5. Update materials (SW entering separate TTs in Materials DB)
6. Update Assessment Information. Need to also add update MMPI-2-RF TM info (TT #6552)--WILL BE ADDRESSED IN 2.7 (TT #6682)
New test copyright (see PDD for formatting instructions and report copyrights):
MMPI®-A (Minnesota Multiphasic Personality Inventory®-Adolescent)
Copyright © 1942, 1943 (renewed 1970), 1992 by the Regents of the University of Minnesota. All rights reserved.
MMPI and Minnesota Multiphasic Personality Inventory are registered trademarks and MMPI-A and Minnesota Multiphasic Personality Inventory-Adolescent are trademarks of the University of Minnesota. Pearson, the PSI logo, and PsychCorp are trademarks in the U.S. and/or other countries of Pearson Education, Inc., or its affiliate(s).
-----------
Peer reviewed 6597 and 6552. Everything looks great.
Verified reports in 2.6.1.
Diffed SLang and looked for missed implementation. All OK.
Png were all updated. Copyright statements were updated.
PDDs were updated. Performed diff. All OK.
rts 8/23/10
|
|
3 - Normal
|
6598
|
Request: Revision
|
MBMD Bariatric Norms - Changes to Q Local - SD
|
Make appropriate changes to Q Local for the MBMD Bariatric Norms/Answer Sheet changes
11/12/09 rts
===================
03/29/2010 - gdb
Added necessary SLang variables and corresponding lookup tables for chronic pain percentile variables. Also made corresponding changes to XMLBasicFunctionality tests. Can't do much more than this (other than to update basic scoretesting) until we cut a branch for 2.6 development.
|
|
3 - Normal
|
6644
|
Change/Defect
|
MTxUtil.calculateAge is incorrect in rare cases
|
Jen Bergan stumbled onto this during her BASC-2 testing.
There is a method called MTxUtil.calculateAge, which appears to be used exclusively to populate the reserved 'AGE' field/array in SLang classes. Under the following conditions:
1) A user takes a test on her birthday.
2) The user was born after February 29 on a leap year.
The method calculates the user's age incorrectly. For example, a user born on 4/14/2004 taking a test on 4/14/2010 will have her age calculated as 5, when in fact she just turned 6.
The fix to this problem is to improve the logic in MTxUtil.calculateAge to compare months, then days in the month, in order to determine whether the user has already had her birthday, rather than simply comparing days in the year.
===============
UPDATE:
Fortunately, the ScoreComputer *does* calculate age correctly in all cases. Perhaps as a result of this bug, it appears that ALL assessments actually rely on the ScoreComputer for age computation, except for the following:
16PF5
All flavors of BASC
IDEAS
MIPS
MMPI-2-RF
OASES
T-JTA
So when testing, you should only expect to see the bug in the assessments listed above.
|
|
3 - Normal
|
6659
|
Change/Defect
|
MBMD Bariatric Summary edit
|
Change the Bariatric Summary code listed to match the Presurgical Summary code listed per John Kamp and authors.
Be Released Ahead of Schedule from the Hospital.
Bariatric Summary
[IF BR_B>89 OR BR_C>89 OR BR_J>89 THEN] {"Low"}
[ELSEIF BR_EE>89 OR BR_4>84 OR BR_5>84 OR BR_7>84 OR BR_G>89 THEN] {"High"}
[ELSE] {"Average"}
Pain Presurgical Summary
[IF PS_EE>89 OR PS_B>89 OR PS_C>89 OR PS_G>89 OR PS_J>89 THEN] {"Low"}.
[ELSEIF PS_4>84 OR PS_5>84 OR PS_7>84 THEN] {"High"}.
[ELSE] {"Average"}
06/03/10 rts
------------------
Fixed and unit tested. Diffed SLang.
TRQ attached.
Tested Low using ID 46
Tested High using ID 28 (pre)
Tested Average using ID 1 (pre)
8/5/10 rts
----------
Verified in 2.6.1. Ready for peer review. 8/5/10 rts
|
|
3 - Normal
|
6660
|
Request: Enhancement
|
LD Clinical norm group doesn't apply to clinical reports, the user isn't notified until the end of the test when user selects to print a Clinical report
|
PDD: pg 102 states "The LD Clinical norm group does not apply to the Clinical Indices."
Steps:
At the beginning of the BASC-2 asmt the user is allowed to select a the norm group of 'LD Clinical', and administer the asmt.
The user is allowed to select to score & report a 'Clinical Report',
Select 'Continue', Report Status window displays - be sure you have report usages
Select "OK" button and the Invalid Report window displays with the message "The report is invalid because LD Clinical - xxx norm groups are not available for the Clinical Indexes. To generate a valid report, you must either select a different report type of edit the administration so a differen norm group is selected."
See attached
I suggest a note be added to the norm group window at the beginning that selection of LD Clinical is not a valid selection for a Clinical report or something like that that is user friendly
======================
(gdb - 8/2/2010)
After discussion with Steve Prestwood, it was agreed to modify the labels for the LD Clinical Norm group to read:
'LD Clinical - Combined Sex (Note: Not valid for Clinical Report)'
'LD Clinical - Separate Sex (Note: Not valid for Clinical Report)'
This change only applies to the TRS-A, TRS-C, PRS-A, PRS-C, SRP-A and SRP-C forms. The remaining forms (TRS-P, PRS-P, SRP-I and SRP-COL) do not support LD Clinical Norms.
|
|
3 - Normal
|
6661
|
Change/Defect
|
BASC 2 Progress Report - ther error message for too many reports is not accurate for BASC 2 found in 2.5.7
|
TO Dave
I created four PRS-A assessment records for the same person. However, for three of them I did not run a clinical or interpretative or score report. So when I selected progress report this is what I got for a message -see image
Title: Too Many Records
Msg: "Progress reports can use a maximum of 5 assessment records. Please cancel out of the print report window and select 5 assessment records or fewer for this report."
Where did the number 5 come from? Also, according to the PDD the maximum is 3 records, not five and I picked four.
From Dave
Problem 1: Yes, this error message is incorrect. We have now tripped over another Q Local legacy bug --- namely, even though it's possible to specify a maximum number of reports to contribute to a progress report (anything from 2 to, presumably, 1 million), it appears that "the maximum is five" managed to congeal into conventional wisdom at some point during the Q Local development timeline. In particular, Q Local correctly determines that the maximum number of reports which can contribute to a BASC-2 progress report is THREE, but unfortunately the error message has the number '5' hard-coded into it.
So as things currently stand, this is the error message we will see whether the true maximum number of reports is 3 (as in the case of the BASC-2), or 5 (as in the case of all other reports on the platform), or 700.
|
|
3 - Normal
|
6664
|
Change/Defect
|
Remove 'Print Intervention Summary' as a report option for SRP-COL
|
In the 2.5.7 Q Local build, 'Print Intervention Summary' is presented as a vliad report option for the BASC-2 SRP-COL assessment. However, section 3.9 of the PDD specifies 'The Intervention Summary is not offered for the SRP-COL form'. So the report option should be removed as a valid option for SRP-COL assessments, and Table 260 of the PDD should be updated to note that 'Print Intervention Summary' is not a valid report option for SRP-SOL.
|
|
3 - Normal
|
6665
|
Change/Defect
|
Links not working for CAInv-Enh Profile, CAInv-Enh Interpretive
|
Discovered during final release testing of Q Local 2.5.7, but appears to have been present in the platform long before that.
Due to an extra leading space character in the URL for CAI, attempts to follow the URL from within Q Local fail. The database as_CAI-V.sql needs to be modified so that the leading space character is removed, and the upgrade SQL for the 2.6 and subsequent releases needs to replace the erroneous URL string with a corrected one.
|
|
3 - Normal
|
6670
|
Change/Defect
|
BASC-2 Clinical Report - changes from Editorial
|
Make Editorial Changes to the Clinical Summary.
Made changes and reviewed. Diffed Slang (check revision 20 vs. 22). Ready for Peer Review. 8/19/10 jsb
|
|
4 - Low
|
3419
|
Change/Defect
|
GAMA: Export element references Scale(Misc)//Emp1_1 and others when Scale(Misc)/Emp1_1 would suffice.
|
Export elements use the // syntax in many cases where the single / would suffice. This assumes that there are no plans on burying the child nodes any deeper than they currently are. This is a minor deal, but using the single / might improve the efficiency.
|
|
4 - Low
|
3425
|
Change/Defect
|
Export - Dates need to have error check added for valid range
|
An end user can enter dates that are a backward range 11/22/2004 - 11/08/2004 and it does not give an error message. A check in the code needs to be added to make sure the end date is newer than the start date for both the administration dates and the created in system dates.
--------
1.1.8 - issue still exists
-Jennifer
===
Issue still exists in 1.2.7. See Export Scored Records 2 test case. rjcm, 8/8/05
-----
7/5/06 - JW - Issue still exists in 1.5.7 (but Defect 3529 fixed).
|
|
4 - Low
|
4108
|
Change/Defect
|
View Messages from Automatic Processes: Disable delete options if no messages are present
|
View Messages from Automatic Process - If no messages are present, the delete option should be disabled.
|
|
4 - Low
|
4357
|
Change/Defect
|
Disable View All Records in Battery when the record is not in a battery
|
The menu item 'View All Records in Battery' should be disabled when the record is not in a battery.
Currently a error message appears.
Title: Q Local System
Message: This record is not a part of a battery.
Buttons: OK.
The 'View All Records in Battery' option can be selected by clicking Manage: View All Records in Battery, right clicking on the record and then clicking on View All Records in Battery, or pressing Alt A then pressing B.
|
|
4 - Low
|
4360
|
Change/Defect
|
Menu item - Save Client Demographics from Assessment Record - grammar
|
The menu item, 'Save Client Demographic from Assessment Records', sounds odd. I believe it should 'Save Client Demographics from Assessment Records'.
Go to Assessment Records - Folders window.
1) Click Enter: Save Client Demographic from Assessment Records
2) Right click on a record and in the submenu click Save Client Demographic from Assessment Records
|
|
4 - Low
|
4362
|
Change/Defect
|
Enter Assessment Records Manually window - grammar
|
pkt 6/19/08 Below we have 2 opinions: the original one states that "Record" should be plural throughout the "Enter Assessment Record Manually"; the other states "Record" should be singular.
The issue/concern is that it displays both ways which makes the product inconsistant. I have to agree that it should be SINGULAR for the reasin that only one record can be entered one at a time.
Is this a fix that we want to do or should it be closed and not addressed?
This is a management decision!
======
1) Go to the Assessment Records - Folder view
2) Click Enter: Enter Assessment Records Manually
3) The Enter Assessment Records Manually window appears with the title 'Enter Assessment Record Manually' - Records is missing an S.
====
This should probably be 'Enter Assessment Record Manually' (without the S) throughout since you can only enter one record manually at a time. Note that this also applies to the tag text that appears when you hover over the Enter button in the toolbar. rjcm, 7/5/05
|
|
4 - Low
|
4383
|
Change/Defect
|
Assessment Records - Confirm Record Delete warning message - bad grammar
|
The warning message for Confirm Record Delete has bad grammar which can make it confusing.
Title = Confirm Record Delete
Message = Are you sure you want to remove the selected record to the Recycle Bin?
Buttons = Yes or No
Either make it 'move the selected record to the Recycle Bin' or 'delete the selected record and move it to the Recycle Bin'.
|
|
4 - Low
|
4392
|
Change/Defect
|
View Change History - 'Manual Entry' is listed as 'Key Entry'
|
1) Go to the Assessment Records - Folders view window
2) Select a record that was manually entered into the system and click Manage: View Change History.
3) 'Key Entry' is listed but it should be 'Manual Entry'
=========================
(gdb - 4/21/2010)
This is an easy change to make, but it is a database change --- specifically, we need to run the following SQL:
update mtx_code set description='Manual Entry' where mtx_code_id=20
In particular, this SQL must be added to the upgrade SQL for the 2.6 release. Since we are not yet to the stage in the 2.6 release where we can write the upgrade SQL (as a best practice, this should not occur until 2.5 is released), work on this track item will be delayed until that time.
|
|
4 - Low
|
5728
|
Change/Defect
|
Able to resize the <Change Batch ID/Name> window and should not be resizeable
|
The &lt;Change Batch ID/Name&gt; window can be resized. However, the displayed information in the window does not resize. This means the window can be resized to selected size, but the actual display (message and buttons) remains the same size in the upper-left of the window (see attached screenshot).
This may be related to Test Track 5692 that was previously closed as this issue was not found during retesting of this test track.
|
