NIH | National Cancer Institute | NCI Wiki  

Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: Migration of unmigrated content due to installation of a new plugin
Wiki Markup
{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) | Init1pm8 \\ |
| *Originator/Customer's Name*: | [Denise Warzel|mailto:warzeld@mail.nih.gov] : [forum posting|https://cabig-kc.nci.nih.gov/Vocab/forums/viewtopic.php?f=44&t=98] |
| *Originator/Customer's Company*: | NCI |
| *Stakeholder Community*: \\
Enter appropriate category of stakeholder from Primary Stakeholders:
* Software and Application designers and architects
* Software and Application engineers and developers
* Scientific and medical researchers
* Medical research protocol designers
* Clinical and scientific research data and metadata managers
* Clinicians
* Patients
* Medical research study participants
* Broader Stakeholders: caBIG® Community WS NIH projects and related commercial COTS vendors (caEHR, SDO's (HL7, CDISC); International Collaborators (e.g NCRI, cancerGrid, China), Government and regulatory bodies (FDA, CDC, ONC) \\
_[_(link to view SemConOps Stakeholders description_|Semantic Infrastructure Concept of Operations Stakeholders])._ | * Software and Application engineers and developers
* Clinical and scientific research data and metadata managers |
| *Summary of requirement pre-interview, by Reviewer:* | The creation of metadata is currently a manual iterative process that involves many discussions, emails, and decisions between the Metadata Modeler and Metadata Curator.&nbsp; This process can occur in the timespan of days or weeks, and complex metadata can involve many modifications and loadings during that time.&nbsp; It is highly desirable that there is a mechanism to track these discussions, decisions, and changes over time.&nbsp; This will provide traceability, as well as a controlled way to review the history of changes for all artifacts involved in compatibility review. \\ |
| * *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 Template
* Review by Originator |
\\
{scrollbar:icons=false}