 |
Page History
| Wiki Markup |
|---|
{scrollbar:icons=false}
h1. { |
| Scrollbar | ||
|---|---|---|
|
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 |
...
---
\\ (eventually linked to Use Cases) | --\- | | *Originator/Customer's Name*: |
...
Init1pm4
| Init1pm4 | | *Originator/Customer's Company*: |
...
| [Tejas Dave |
...
|mailto: davet@mail.nih.gov |
...
]: [forum |
...
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
- Scientific and medical researchers
...
Summary of requirement pre-interview, by Reviewer:
...
Using Natural Language Processing and integrating both EVS and caDSR APIs or similar future services, create a discovery service/tool which exposes data elements not based on the Names stored in caDSR but by using query in a concept search and pulling associated Administered Components from caDSR to match. This would enable construction of better search algorithms and serve as a potentially better discovery entry point for the user not familiar with the ISO 11179 nomenclature. The primary users that this would serve include both Cancer Researchers and Information Technologists.
...
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
...
posting|https://cabig-kc.nci.nih.gov/Vocab/forums/viewtopic.php?f=43&t=157]\\ |
| *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 designers and architects
* Scientific and medical researchers |
| *Summary of requirement pre-interview, by Reviewer:* | Using Natural Language Processing and integrating both EVS and caDSR APIs or similar future services, create a discovery service/tool which exposes data elements not based on the Names stored in caDSR but by using query in a concept search and pulling associated Administered Components from caDSR to match. This would enable construction of better search algorithms and serve as a potentially better discovery entry point for the user not familiar with the ISO 11179 nomenclature. The primary users that this would serve include both Cancer Researchers and Information Technologists. \\ |
| *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} |
