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

Create discrepancy lists for automatic query generation #159

Open
DrEspresso opened this issue Feb 4, 2020 · 4 comments
Open

Create discrepancy lists for automatic query generation #159

DrEspresso opened this issue Feb 4, 2020 · 4 comments
Labels
enhancement New feature or request

Comments

@DrEspresso
Copy link
Contributor

Is your feature request related to a problem? Please describe.
In the traditional clinical Monitoring process, a monitor creates a "query" on an item of a specific secuTrial form and asks an investigator to correct data and answer the query. When the investigator changes the status of the query to "answered", the monitor can mark the status as "resolved". This is a tedious taks if the same or similar queries need to be created for mulitple patients.

Describe the solution you'd like
I'd like to take advantage of secuTrials "Discrepancy Transfer Module", where one can upload "discrepancies" as .csv file, which secuTrial converts into automatically generated queries.

Additional context
@benkertp implemented functions for this in the "old" secutrial.R package used at CTU Basel. I used them once to create queries for a cohort study.

Note: If "DEC" is enabled for the study, queries can only be created on forms that have been marked as "closed".
Also, once a query has been created on a form, any data changes on that form can only be performed on questions that have an open query.

@aghaynes aghaynes mentioned this issue Feb 4, 2020
@aghaynes
Copy link
Member

aghaynes commented Feb 4, 2020

Interesting idea. Could be very useful for central data monitoring...

@DrEspresso
Copy link
Contributor Author

Interesting idea. Could be very useful for central data monitoring...

Yes, that's our current need 👍

@PatrickRWright
Copy link
Collaborator

Would you like to implement this @DrEspresso ? If yes, then I will assign you to this issue. If you are not sure if it will be you or rather someone else, a few more specifics regarding the functions may be useful.

@PatrickRWright PatrickRWright added after 1.0.0 enhancement New feature or request labels Feb 4, 2020
@DrEspresso
Copy link
Contributor Author

@PatrickRWright I will have a look. It depends whether we need this for a project in the next two weeks or not. Also, maybe a refactoring of @benkertp's code is all that is needed, in which case it might be not much additional work.

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

No branches or pull requests

3 participants