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

Export clinical data model as REDCap-compatible format #499

Open
anngvu opened this issue Aug 19, 2024 · 3 comments
Open

Export clinical data model as REDCap-compatible format #499

anngvu opened this issue Aug 19, 2024 · 3 comments
Labels
enhancement New feature or request

Comments

@anngvu
Copy link
Collaborator

anngvu commented Aug 19, 2024

@cconrad8 and I had a REDCap-related discussion which led to nice feature that should probably be made possible. This only applies to the clinical template, not the assay data templates.

User stories:

  • I'm already bringing in several other REDCap clinical data models. How do I compare them with NF's experimental clinical data model, which has chosen/implemented https://dash.harvard.edu/bitstream/handle/1/32725809/Neurology-2016-Hanemann-S40-8.pdf [^1], to better understand the translation or gaps between these standards?
  • How do I use NF's clinical data model as a questionnaire in my REDCap database? (DCA is not for collecting clinical data at the clinical trial site or point-of-care!)

To help with these, we should have a way to export the clinical component in REDCap .csv format. This serialization follows a specific structure (just as schematic .csv follows a certain structure). The investigator gets a .csv in the REDCap format with which they are familiar [^2]. If they want, they can also plan their clinical study to use the recommended questionnaire by loading in the recommended schema. Note: we need a REDCap instance to test out the loading.

Benefits:

  • That way, when clinical data is contributed back to NF, there is no translation needed because the recommended schema was used from the start.
  • The original paper made the clinical data collection recommendations but did not conveniently provide it as a reusable REDCap schema to make implementation easier for others (at least, it wasn't mentioned in the paper). By doing so and perhaps providing even more serializations that interoperate with clinical data collection tools later on, this can encourage penetration of schema in new projects.
image image

Footnotes

  1. Hopefully choosing this was a good choice.
  2. We don't want to give them YAML or JSON-LD -- YAML is readable but for developers; JSON-LD is for software.
@anngvu anngvu added the enhancement New feature or request label Aug 19, 2024
@allaway
Copy link
Contributor

allaway commented Aug 19, 2024

💪

@anngvu
Copy link
Collaborator Author

anngvu commented Aug 19, 2024

Potentially contribute back to REDCap Shared Library

@cconrad8
Copy link
Contributor

cconrad8 commented Aug 19, 2024

Useful links:

Redcap training module to test out loading:

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
Status: No status
Development

No branches or pull requests

3 participants