Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Proposed/Required Protocol Changes: #16

Open
6 of 8 tasks
yatharthranjan opened this issue Dec 10, 2018 · 3 comments
Open
6 of 8 tasks

Proposed/Required Protocol Changes: #16

yatharthranjan opened this issue Dec 10, 2018 · 3 comments

Comments

@yatharthranjan
Copy link
Member

yatharthranjan commented Dec 10, 2018

  • - Add a Time Window property to questionnaires to know how long a questionnaire can be shown/answered. Similar to Timeout of a questionnaire should be configurable in protocols #7
  • - Add Audio Questionnaires
  • - Fix Clinical Tasks protocol - repeatAfterClinicVisit and unitsFromZero (whether this is from midnight of the next day or other)
  • - ESM have questionnaires that vary if it is the first ESM of the day or the last ESM of the day. This needs to be incorporated in the protocols as metadata that should then be used in the app instead of hard-coding it.
  • - Timing of repeats of questionnaire is +1 hour because of app code
  • - We should also add a “hasOnlyInfo” flag in the protocols so that tasks like Thinc IT are handled correctly.
  • - Investigate if possible to add the recording timeout of audio questionnaires somehow in the protocol.
  • - Some of the above entail having meta-data about the questionnaires. It may be a good idea to think about adding a generic meta-data field and how to interpret it in the app.
@mpgxvii
Copy link
Member

mpgxvii commented Aug 16, 2019

This has been added.

  • Add Audio Questionnaires

This has been released to a project (STAGING_PROJECT) and will soon be released to sites (protocols have been added but not released).

  • Fix Clinical Tasks protocol - repeatAfterClinicVisit and unitsFromZero (whether this is from midnight of the next day or other)

zero in unitsFromZero in the app is currently handled as current time. So if unitsFromZero is 7 days, then this will be 7 days from clinical task generation.

  • ESM have questionnaires that vary if it is the first ESM of the day or the last ESM of the day. This needs to be incorporated in the protocols as metadata that should then be used in the app instead of hard-coding it.

This still needs to be fixed (RADAR-base/RADAR-Questionnaire#443).

  • Timing of repeats of questionnaire is +1 hour because of app code

This has been fixed in the app and modified in the protocols.

  • We should also add a “hasOnlyInfo” flag in the protocols so that tasks like Thinc IT are handled correctly.

I'm not sure what you mean by this @yatharthranjan.

  • Investigate if possible to add the recording timeout of audio questionnaires somehow in the protocol.

This is not needed anymore with the addition of start and stop buttons for audio tasks.

  • Some of the above entail having meta-data about the questionnaires. It may be a good idea to think about adding a generic meta-data field and how to interpret it in the app.

Yup similar to RADAR-base/RADAR-Questionnaire#443

@mpgxvii
Copy link
Member

mpgxvii commented Feb 26, 2020

Updated list of protocol changes requested:

  • Repeatprotocol should allow scheduling by day of the week and randomly

  • Should have ScheduleCoverage or how far in the future to generate schedule for
    Or better start and end for assessment schedule for startTime and endTime

  • Clinical tasks should be generalized to always on or on demand questionnaires for tasks/questionnaires that can be filled out anytime (custom title on the page, and possibly translations as well) by adding type key or something else

  • Questionnaire filters: hiding/showing questions of a questionnaire based on conditions

  • Separate questionnaire startTime from notification time, or option of not scheduling notifications

@blootsvoets
Copy link
Contributor

Could you please make separate issues out of these? That will make it easier to see what independent changes would be useful.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants