NIH | National Cancer Institute | NCI Wiki  

Error rendering macro 'rw-search'

null

Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: Migrated to Confluence 4.0
Wiki Markup
{scrollbar:icons=false}
h1. {
Scrollbar
iconsfalse
page-info

...

Pre Interview:

...

Item

...

Information/Response

...

Date

: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

...

Init1pm9

 \\
(eventually&nbsp;linked to Use Cases) | Init1pm9 \\ |
| *Originator/Customer's Name*:

...

 | [Salvatore Mungal|mailto:salvatore.mungal@duke.edu] : [forum

...

 posting|https://cabig-kc.nci.nih.gov/Vocab/forums/viewtopic.php?f=44&t=143]\\ |
| *Originator/Customer's Company*:

...

 | Duke Cancer

...

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).

...

  • Software and Application designers and architects
  • Medical research protocol designers
  • Clinical and scientific research data and metadata managers

...

Summary of requirement pre-interview, by Reviewer:

...

The forum posting summarizes a number of use cases that pertain to Metadata Modelers and Cancer Researchers discussed during a caBGI face-to-face meeting at Cambridge.  They can be summarized as follows:

...

Recommended Next Step Enter one: Follow-up interview, Observe, Use Case Template (text), Use Case Model (formalized/UML diagram), Group Discussion, Prototype, Waiting Room

...

Follow-up interview

...

 Center \\ |
| *Stakeholder Community*: \\
Enter appropriate category of stakeholder from Primary Stakeholders:&nbsp;&nbsp;
* 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 designers and architects
* Medical research protocol designers
* Clinical and scientific research data and metadata managers \\ |
| *Summary of requirement pre-interview, by Reviewer:* | The forum posting summarizes a number of use cases that pertain to Metadata Modelers and Cancer Researchers discussed during a caBGI face-to-face meeting at Cambridge.&nbsp; They can be summarized as follows:
* Automation
** Streamline the process of model creation, submission, and curation, including the tracking of artifacts (this is similar to [Init1pm8 - Simplify and streamline recording data semantics], [Init1pm6 - Automate Loading process], and [Init1pm7 - Automate & Streamline caDSR Model Submission Process])
* Enhanced Semantics
** Model/mechanism to drive through the questions on a form or during a task without manually curating CDE (need more clarity)
** Change choices on subsequent question answers based on answer to another question. More complex form of skip pattern or conditional behavior - event driven vs. skip pattern - NHS.
* Enhanced Tooling Features
** Import electronic doc/forms to caDSR.
** Improve searching for "best" CDE version (artificial intelligence - not trivial). |
| *Recommended Next Step* Enter one: Follow-up interview, Observe, Use Case Template (text), Use Case Model (formalized/UML diagram), Group Discussion, Prototype, Waiting Room | Follow-up interview \\ |
\\
{scrollbar:icons=false}