Participation Status Flag Bug

[robertsamm]

Placeholder for requirements.

In Nov/Dec release, @kmazzilli identified an issue on the SMDB (see original github issue thread here: #1437 (comment)) where if a pt already has an activity refused (e.g. refused all future activities) and then has a suspended contact entered for them in the SMDB, the participation status' variable' is reverted back to 'no refusal'.

We will want to revisit the code and discuss with @FrogGirl1123 intended outcome before finalizing requirements.

Will not be included in Jan Release.

[robertsamm]

Meeting scheduled for 2/19

[brotzmanmj]

On mid-week call today: Agree to fix derived Participation Status variable so that suspended contact does not affect it in any way. Autumn will check dictionary to see if it accurately captures the exclusion of suspended contact from this definition. Also check the reversion of this variable on reversion of refusals and withdrawal.

[hullingsag]

Hi all, I've review the DD documentation for the participation status variable (SMMet_PartStatus_v1r0; CID: 912301837).

The notes column states that the "Row of derivation is on same row as corresponding response variable."

The derivation notes specify that:
HdRef_Basesrv_v1r0 equals 0 AND HdRef_Baseblood_v1r0 equals 0 AND HdRef_Baseurine_v1r0 and HdRef_Basesaliva_v1r0 equals 0 AND HdRef_Allsrv_v1r0 equals 0 AND HdRef_Allsample_v1r0 equals 0 AND HdRef_BlSpecSrv_v1r0 equals 0 AND HdWd_WdConsent_v1r0 equals 0 AND HdWd_Activepart_v1r0 equals 0 AND HdWd_HIPAArevoked_v1r0 equals 0 AND HdWd_Destroydata_v1r0 equals 0 AND HdWd_Deceased_v1r0 equals 0

Confirming that the suspended contact variable (HdWd_WhoRequestSuspend_v1r0; CID: 719222792) is not part of the participant status variable derivation.