NIH | National Cancer Institute | NCI Wiki  

Pre Interview:

Item

Information/Response

Date

12/10/2009

Requirement # unique id <SemCon Ops Initiative>.<analysts initials><requirement number>
e.g. Init1dbw1
(eventually linked to Use Cases)

Otherdbw1

Originator/Customer's Name:

CBIIT Customer Liaison: Margaret Haber
CDISC Rhonda Facile - CDISC liaison to NCI on the SHARE project. Responsible for the consolidation and delivery of all requirements that CDISC will provide as well as the primary contact for any other project related information dissemination or issue resolution, Please work through Margaret to set up meetings.                                                                                        

Originator/Customer's Company:

CDSIC / Margaret Haber

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


SDO

Summary of requirement pre-interview, by Reviewer:

NCI has stated to CDISC is that if they submit their requirements to us during our build, they would be incorporated as our requirements. With the caveats that:

-        all requirements cannot be met in the first iteration, it will be a process
-        due to the distributable nature of what we plan to build, we made no assumptions about hosting
-      there could be one to many terminology servers and repositories serving NCI, CDISC or others

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

Review and decompose into Use Case Templates for the attached documentation, schedule follow up through Margaret Haber


  • No labels