SDC+-+CDE+Attributes+and+Form+Requirement

include component="page" wikiName="siframework" page="Structured Data Capture SidebarRight" include component="page" wikiName="siframework" page="space.template.inc_contentleft_begin" include component="page" wikiName="siframework" page="Structured Data Capture PageTabs"

The requirements we’ve discussed include the need for dynamic, flexible, intelligent forms (template models) that can efficiently manage—i.e., capture, validate, store, and transmit—wide diversities of ever-evolving data sets obtained from multiple sources and input methods. The forms should be relatively easy for collaborators to create and evolve, and should control for versioning. In addition, they should have the mathematics and logic capabilities required to execute algorithms that tailor the user interface to the particular set CDEs being captured, deliver the results efficiently and securely, and be linked to the analytical models that aggregate and analyze the data. As such, each form should, at minimum: In addition, I contend that the CDE attributes should include the following metadata:
 * Be readily updated to accommodate changing CDEs and value sets
 * Handle versioning competently
 * Have robust macro/script automation capabilities
 * Be structured in a manner that reflects its corresponding analytical model
 * Have a wide variety of user interface capabilities, e.g., present CDEs one per page (one at time) as well as multiple items on a single page
 * Be able to query databases and parse structured text files (including XML, delimited text, and csv)
 * Enable branching logic based on a single criterion or combination of criteria
 * Be able to auto-calculate values (e.g., determining age from birth date and perform numeric conversions)
 * Provide warnings for missing or invalid inputs
 * Be able to run on a desktop
 * Be able to use the basic Direct transport method (SMTP + S/MIME).
 * 1) CDE ID number
 * 2) Question to be answered
 * 3) Presentation order of CDE in sequence of CDEs (for branching and logical flow purposes)
 * 4) Response scale (i.e., set of acceptable responses to the CDE)
 * Standardized terminology/code Value Set used (if any)
 * Identification of source
 * Version IDb.
 * Other response types (e.g., T/F, Y/N, specified range of numeric responses, etc.)
 * 1) Response format
 * 2) Response validation criteria (e.g., to assure proper format, within numeric range, etc.)a. Warning/Alert message if invalid response or required response is missingb. Process for handling invalid or missing response
 * 3) Branching logic, if any, that indicates the next CDE to present based on response(s) to previous CDE(s)
 * Branching criterion is required, which indicates the particular CDE response (range) to trigger the branching process; the criterion may be based on a response to a single previous CDE or to multiple CDEs
 * <span style="font-family: Arial,Helvetica,sans-serif;">Branch-to indicator designating the next CDE to present if the branching process is triggered
 * 1) <span style="font-family: Arial,Helvetica,sans-serif;">Map of the CDE to the CCDA for EHR queries.

Information provided by Stephen Beller, Ph.D. include component="page" wikiName="siframework" page="Structured Data Capture Contacts" include component="page" wikiName="siframework" page="space.template.inc_contentleft_end"