muccg / rdrf

The Rare Disease Registry Framework (RDRF) is an open source tool for the creation of web-based patient registries.
GNU Affero General Public License v3.0
15 stars 8 forks source link

Staging 6.6.46 testing - bc issues #2444

Closed id2359 closed 1 year ago

id2359 commented 1 year ago

Missing data alternative use cases

BC – issues as below

Anil KRISHNAN had no baseline PROMs so I added a 6 month PROMs (3/10/22) directly to the site system as though it was being completed by the nurse during a discussion with the patient (can sometimes occur). At that point Anil had no baseline and no other PROMs completed. The visualisations showed this 6 month follow up as the 3rd follow up with all previous entries as missing (1st screenshot). This was good as it showed the baseline missing but the 6 months follow up is the 1st f/up in breast. I then added the 12 month f/up (1/4/23) via QR code and found that this pushed the 6 month f/up down to 2nd f/up and put the 1 year f/up to 3rd f/up (screen shot 2 below). Baseline is still shown as missing (good and better than LC where it is shown to have data in it)) but 6 month and 1 yr should show as f/up 1 and 2 respectively. The order is correct as I made the responses more severe for the 1 year and this is seen as the later f/up.

id2359 commented 1 year ago

download

id2359 commented 1 year ago

download (2)

id2359 commented 1 year ago

I also see misordering for the case when there is a single baseline proms form saved. This gets misorderd to the last column

id2359 commented 1 year ago

The fix for baseline with empty collection date causes issues for BC which has multiple followup forms in the main context.

E.g.

Scenario

B[d] FU6M[None] FU1Y[None] FUY2[None] now gets ordered

FU6M[None] FU1Y[None] FUY2[None] B[d] as the null collection date in the empty form gets put first ( which works in the other registries.)