search

ctsit / imagemap

Imagemap REDCap external module
Other
13 stars 26 forks source link

Data entered on survey disappearing when using @IMAGEMAP action tag (REDCap 9.4.1, Imagemap v1.4.4) #49

Open jrpence opened 4 years ago

jrpence commented 4 years ago

Issue by jcjohnsonmo Mon Feb 10 18:05:25 2020 Originally opened as https://github.com/marlycormar/imagemap/issues/13

The issue here is that I had data entered into a survey that was disappearing when I went to the next page. At Rob Taylor's suggestion, I determined that this issue is resolved when the @ImageMap action tag is removed. The screenshots are provided below and the demonstration xml file is available on the REDCap Community page: https://community.projectredcap.org/questions/78059/data-entered-on-survey-disappearing-due-to-section.html .

Project Design: I have 2 instruments, Pre and Post. In both instruments, I have an imagemap (@ImageMap=DO_TOUCH_NET_BODY_GREY) and fields for each body region where the severity of the pain is assessed, if the body region is selected on the imagemap. Additionally on the Post instrument, there is a matrix field where the rows show up if the severity on the Post instrument is worse than the severity on the Pre instrument.

Issue: When more than one body region has worse severity, only the first one in the list shows up in the matrix field. Additionally if you return to the previous page on the Post instrument, the severities for the other body regions have disappeared. This behavior only happens in Survey Mode, not Data Entry Mode.

Notes: After many hours of testing, @frgeof and I found how to prevent this from happening. Method 1: Change the survey setting Question Display Format to "All on one page". Method 2: Change the matrix field to separate fields and remove the Section Break. Additionally at Rob Taylor's suggestion, we found that removing the @ImageMap action tag on the Post instrument solves the issue.

S1 S2 S4 S5 S6 S7

jrpence commented 4 years ago

Comment by marlycormar Thu Jul 16 00:36:08 2020

Hi @ChemiKyle! Can you check out this issue and see if it is still of interested?

jrpence commented 4 years ago

Comment by ChemiKyle Thu Jul 16 13:08:09 2020

@jrpence

jrpence commented 4 years ago

Comment by jrpence Fri Jul 17 19:53:08 2020

This issue seems to be caused by the branching logic. With the DO-Touch.net image map putting the data in a text field, I was repeatedly hit with warnings that fields with values are being hidden and should be erased. If you change the DO-Touch.net image map to a checkboxes field (with 01-59 as valid answers) and base the branching logic off of those values (ie.For the Face field the logic is [bodymappre(01)] = "1" ) then you will not get hit with the questions every page load. The warning happens if you have data in the body part specific question and then remove that part from the image. It seems that pulling that data out of the text with contains causes the survey to repeat its warnings about clearing the data fields that are “hidden from view”.

jcjohnsonmo commented 4 years ago

This issue is not related to getting warnings. The data "disappears" when you keep the same body parts selected that were previously selected (ie, you don't remove any body parts from the image). Also, note that this is not specific to the DO-Touch.NET image map. I had the same experience with the PAINMAP-FEMALE. (I did not try any others.)

With that being said, changing to checkboxes does seem to fix the problem. Unfortunately, it causes a different problem with the @DEFAULT action tag passing data from 2 different events, which was solved by using the text field. Since I have a workaround that functions (placing the imagemap in a separate instrument and using the auto-continue to next survey), I will keep the imagemap as text. However, it still seems to me that there's an issue with @IMAGEMAP.