Categories
- 6.2K All Categories
- 279 Discussions
- 173 General Discussion
- 21 Roadmap & New Feature Ideas
- 28 Add-Ons & Code Contributions
- 57 Forum How-Tos
- 1K Q & A
- 223 Installation & Setup
- 386 Study Build, Rules, and CRFs
- 138 Data Entry, Monitoring, and Data Management
- 114 Extracting & Reporting
- 12 Regulatory Compliance
- 35 Rule Designer
- 94 Web Services & Integration
- 11 Internationalization and Localization (i18n / L10n)
- 24 Announcements & Updates
- 24 Announcements & Updates
- 4.8K Archives
- 3K Users Mailing List
- 1.8K Developer Mailing List
We are currently working on the forum. For the short-term, all forum content will be in read-only format. We apologize for the interruption and look forward to collaborating with you shortly. All the best in your research!
Printing subject case book - possible bug
alan.rossington
Posts: 9 ✭
Hi
We are seeing a strange issue in the subject case book printout. For our adverse event form we have a coded value for the description of the AE (see attached) with values 1-87 for a multi-select drop down box.
A record for a patient exists with values 44 and 58 - this is confirmed in the export and seen on the data entry screen which suggests that the values in the database are correct.
However, we are seeing a number of the multiselect options outputting in the subject casebook print that don't exist in the database. In this case the values coded as 4, 5, and 8 as well as the correct values of 44 and 58 are all output in the print (attached) as being selected which is not correct. I assume this is due to a .contains() routine or something similar which returns true for these numbers.
Has anyone else seen this issue, is there any way round it?
We are seeing a strange issue in the subject case book printout. For our adverse event form we have a coded value for the description of the AE (see attached) with values 1-87 for a multi-select drop down box.
A record for a patient exists with values 44 and 58 - this is confirmed in the export and seen on the data entry screen which suggests that the values in the database are correct.
However, we are seeing a number of the multiselect options outputting in the subject casebook print that don't exist in the database. In this case the values coded as 4, 5, and 8 as well as the correct values of 44 and 58 are all output in the print (attached) as being selected which is not correct. I assume this is due to a .contains() routine or something similar which returns true for these numbers.
Has anyone else seen this issue, is there any way round it?
0
This discussion has been closed.
Comments
That's unusual. Do you have multiple versions of the CRF? Could you share your CRF Excel file? Also PDF or screenshot of the printed casebook. The word document is difficult to understand.
Thanks,
Cal
Sorry for the delayed response, we've been looking into it. It does seem to
be a bug in the Java-script (the good news is that it's not in the ODM /
JSON so the data is good but the representation in the print view has a
bug). We're looking into a fix and will let you know.
Best,
Alicia
On Wed, Oct 8, 2014 at 3:27 PM, ccollins
Hi Cal
Just a single version of the CRF. Excel attached.
PDF of that page of the casebook attached - the first 3 values/ticks for the "Details of Event" shouldn't be there (blisters), they aren't present on the data entry screen nor the export.
Kind Regards
Alan
A fix will be included in the next (post 3.4) release. This was of particularly high importance to us as Print Subject Casebooks is shiny-new functionality. I'm glad this was caught early.
Thanks,
Alicia