⚖ Encode Compatability with NIMH Data Archive

[shnizzedy]

Each object can have the following properties per NDA:

• Element Name,
• Data Type,
• Size,
• Required,
• Description,
• Value,
• Range,
• Notes

You can view each structure page by clicking its name in the Data Dictionary list. This page displays a full list of all the data elements currently supported in the structure and their associated parameters for use in preparing your submission template:

Element Name
Type of data accepted in this element
Size: Character limit of string elements
Required status:
Required elements must* be provided.
Recommended elements are entered if they were collected, otherwise left blank.
Optional elements can be provided at your discretion.
Conditional elements are Required if their conditions are met.
Description
Value range: Anything provided outside of this range provided will cause a validation error
Notes
Aliases: This is the list of valid aliased names usable for this element. Email us to request a new one.
*Please note: Required elements you did not collect will often have an associated value to code for this in your data, and this must be filled in. Check the structure in question for the specific coding.

― NDA Data Structures

• RDoC NDA policy
• NDA data dictionary

[shnizzedy]

Brainverse has to be run locally (or served not-by-the-developers) as far as I know, and is designed to build NDA-compatible instruments.

[satra]

@shnizzedy - even though we used NDA data structures in brainverse, it is not appropriate in the long run and hence using a comprehensive format for form description would be useful.

i think it should support the following features:

• decoupling widgets (view) and data
• support validation requirements
• support conditional logic
• support scoring/workflows on data elements

[shnizzedy]

@satra ― all good points. Does Brainverse currently accommodate any/all of those features?

[satra]

@shnizzedy - not at present in an explicit way - brainverse currently uses NDA schema - but we want to move away from it while supporting export to the schema.

NDA is a data ingestion schema, not a data generation schema.

[shnizzedy]

@satra ― cool, I think we're on the same page. This issue (and ChildMindInstitute/mindlogger-app-backend#23 and ChildMindInstitute/mindlogger-app-backend#24) are intended as necessary-but-not-sufficient minima; ie, things not to contradict without explanation.

When you say you want to move away from NDA schema, do you mean expanding or abandoning? Some of each?