Requirements identification and analysis is ongoing as follows:

• RFI has been issued and responses to RFI have been collected and analyzed.
• Demonstrations are ongoing with second round requested from RFI respondents.
• Demonstrations and RFI responses are currently being mapped to caDSR functional and non-functional requirements.

caDSR Requirements Gathering Process

caDSR is part of the NCI Semantic Infrastructure and current plans are to refresh and extend the infrastructure to align with broader initiatives while preserving and improving current capabilities.  The requirements for caDSR stakeholders has been changing and expanding over the past 5-6 years, however largely we've addressed technology stack, security, and 508 compliance during that time.  In 2014 a decision was taken to rebuild and modernize these services and make it easier to discover the consensus standards and integrate these elements and linked data into cancer research and care workflows. In addition, we have a goal to harmonize our capabilities with broader metadata initiatives nationally and internationally, such as with NLM, ONC SDC CDISC, FDA, AHRQ, and HL7 FHIR.

caDSR tooling requirements arise in many settings. By using one of the means described below you will ensure your ideas have been successfully communicated and documented. Software requests for enhancements are acknowledged by the caDSR team with the creation of an item in our tracking database and assigned a reference number, making it easy to track your favorite request! If it doesn't have a GForge tracker number, we haven't yet realized it as a requirement.

Where requirements come from:

• caCORE Software Users Meetings. Visit the caCORE Users Meetings and Forums wiki page for meeting information, links to past meeting presentations and meeting notes, and links to status and planning information. As the release cycle progresses we begin a public review and prioritization, drawing from variety of factors to make final "in/out" decisions. We conduct user feedback sessions throughout the design and prototype phases.

• Contact us at Application Support or by the "Send comments and suggestions" links from the caDSR tools. All messages are received and logged by Application Support.

• Subscribe to the caDSR Users LISTSERV. Post ideas, participate in discussions. All postings are read, and if a requirement is suggested, it's entered into our tracking system once confirmed.
  
  
• Prior requirements initiatives, some of these are linked to the SI Requirements wiki

• Personal communications: If you have a specific idea or suggestion you want to discuss personally with Denise Warzel (Program Manager for caDSR software) feel free to contact her directly.

caDSR Futures

NCI is planning to modernize the aging caDSR semantic metadata infrastructure to make it more useful, more accessible, easier to integrate into research and care processes and systems, and better support community comment, curation and harmonization of content and data.  While the requirements process has been ongoing, documenting what we have been hearing began last fall, and we are already collaborating and aligning with sister NIH ICs, national, and international metadata initiatives.  We recently decided it would be very useful to seek broad community input via an RFI.  Please see CHILD PAGES below for links to the RFI document and the requirements draft, which will be updated as it evolves with community input.