Can an expected participant data be "hidden" from a participant?

[bardram]

When adding expected participant data to a protocol, you can assign it to either all participants or a specific participant role (like the "father").

But what if you have expected participant data that you want to keep "hidden" from participants? For example, diagnosis, which you don't want the participant to input (they don't know this).

Such participant data should only be added by the researcher in the portal.

Would it, for example, make sense to add a "researcher" role to a study?

The usecase for this is the ICAT study, where the researcher (Jeff) is adding a lot of "internal" notes to a participant.

[yuanchen233]

For ICAT, the participant won't see the expected participant data, simply because ICAT doesn't have UI for it. It is only exposed to the researcher through Portal.

I think this also works for other studies: render only what's relevant to the user on their platform, and expose everything to the researcher through Portal.

Adding a researcher role in the study is an overkill for this requirement in my opinion.

[Whathecode]

The usecase for this is the ICAT study, where the researcher (Jeff) is adding a lot of "internal" notes to a participant.

I seem to remember this was a known use case. I'll have a look at the design whether I have any current or future provision in mind.

Adding a researcher role in the study is an overkill for this requirement in my opinion.

Good consideration. @bardram Is this an access control or usability concern? The former needs core support, the latter can be done as @yuanchen233 suggests.

[bardram]

Good consideration. @bardram Is this an access control or usability concern? The former needs core support, the latter can be done as @yuanchen233 suggests.

It is more of a usability issue or design issue. The scenario is that the researcher (Jeff) is adding a lot of participant data he needs to register, but only part of this can be input by the participant. So, how does the study app (or any other participant-facing application) know what to ask the participant for?

@Panosfunk - How do you select what to ask the patient for in the Study App now?

[Panosfunk]

Currently the expected participant data is defined in the protocol and the researcher can select which ones they are going to include in the app. The diagnosis part, does come in a "group" with Effective date, diagnosis description, icd11 code and conclusion. If we want to hide all of them, we can just remove this step from the app, so that it is still available in the portal, but the participant cannot see it. @bardram

[Whathecode]

I browsed some old issues, and my memory did not betray me:

We have plans to allow researchers to attach data about the participant, using the same mechanism as participant metadata is currently stored per deployment.

... but, those plans never materialized (because it wasn't a priority, not that it didn't make sense).

The idea is to allow the study subsystem to add participant metadata as well (participants don't/shouldn't have access to this subsystem). You may remember designs about the complexity of being able to set some data before deployment, and other data only after, and matching things up upon deployment. That is where this comes from.

Architecturally speaking, this is where we want to be headed, though. That's also what would allow reuse of such data across studies (participant cohorts), setting recruitment targets, etc.

Coming to think of it, didn't CAWS have participant data endpoints just like that before I even added the protocol-defined data? So maybe CAWS supports (or supported) it, just not core (yet).