Page History

{scrollbar:icons=false}
h1. {page-info:title}

h2. Pre Interview:

|| Item || Information/Response ||
| {color:#000000}{*}Date{*}{color}{color:#000000}: {color} | 12/17/2009 |
| {color:#000000}{*}Requirement # unique id{*}{color} _<SemCon Ops Initiative>.<analysts initials><requirement number>_ \\
e.g. Init1dbw1 \\
(eventually&nbsp;linked to Use Cases) | Init1pm13 \\ |
| *Originator/Customer's Name*: | Christo Andonyadis \\ |
| *Originator/Customer's Company*: | NCI \\ |
| *Summary of requirement pre-interview, by Reviewer:* | Medidata is the clinical trials database selected by NCI for use at trial sites.&nbsp; Medidata supports the import and creation of forms by Forms Authors based on common data elements.&nbsp; Associated with this are likely to be a number of use cases on the functionality that Medidata needs for querying and importing CDEs and forms.&nbsp; See attachments for additional information.
* [^NCI Use Case Review_ Labs 20091211.ppt]
* [^NCI HLR  Review All 20091209.ppt]
* [^medidata_notes_20081211.doc]\\
One of the requirements currently not met is the need to be able to   specify that a CDE on a form can have multiple answers selected from the   enumerated value list.&nbsp;&nbsp; Currently this is captured in the Question   Instruction of the Form objects.&nbsp; Users would like to be able to specify   this for the CDE.&nbsp; one approach is to create a Derived Data Element   composed of the number of CDEs that are permitted in the response.&nbsp; this   can be supported in the current 11179 Ed 2 metamodel. \\
Furthermore, it appears that what is needed is a collection of  metadata "things" - forms, CDEs, etc. that are named and have  privileges.&nbsp; There are some in global scope (managed by a certain few  people), a user can create any number of them, and that user can make  his publicly available (say, give me John's public collections, then  give me John's Breast Stdy 123 collection).&nbsp; There would be a service  (API) with these types of functions. |
| *Recommended Next Step* Enter one: Follow-up interview, Observe, Use Case Template (text), Use Case Model (formalized/UML diagram), Group Discussion, Prototype, Waiting Room | Use Case Development (2/3/2010) Assigned to Mohamed \\ |
\\
{scrollbar:icons=false}