Closed fhosking closed 1 month ago
It seems like the issue is related to the encodings of the whichtkipostallobmt in the tblTKIsFailure Access object. We can see that record 23 has 3 and then 2 recorded as the values which at present correspond to our TKI codes, the first 5 of which are:
1, None 2, Imatinib 3, Dasatinib 4, Nilotinib 5, Bosutinib
This relates to this lookup table in Access:
However I can see this lookup table in access which seems to correspond to your reference:
I've switched the encoding to this table for whichtkipostallobmt
Perhaps we also need to do this for other similar fields?
Brilliant! That works for two patients I checked so yes go ahead and and do the same for Auto and DLI.
Updated fields whichtkipostdli and whichtkipostautobmt. What about on Chemotherapy, we have whichtkiid and whichtkipostct?
Yes, for same for chemo.
Updated chemo whichtkiid and whichtkipostct
Looks like Which TKI post-AlloSCT still isn't working. For patient 23 here is the MSAccess and REDCap screenshots:
You can see that in Access Dasatinib is Line 2 but in REDCAP is Line 1.
Just be aware that "Which TKI post-AlloSCT" is different from "Which TKI post-AlloBMT". So clicking yes to "TKI post-AlloSCT" gives you the option to pick only one TKI in "Which TKI post-AlloSCT." "Which TKI post-AlloBMT" gives you the option for several TKI along with option for "Which line of TKI post-AlloBMT." Hope this makes sense otherwise we can set up a teams meeting as it is probably the only major item stopping us from moving to REDCap.