NIH | National Cancer Institute | NCI Wiki  

  • Created by Unknown User (mcconnellp), last modified by Unknown User (wileyal) on Jan 23, 2012

Pre Interview:

Item

Information/Response

Date: 

12/17/2009

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

Init1pm7

Originator/Customer's Name:

Bilal Elahi : forum posting

Originator/Customer's Company:

Unknown

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

Clinical and scientific research data and metadata managers

Summary of requirement pre-interview, by Reviewer:

There is a distinct need to reduce the cost, time, and resources in general for the loading of models/metadata into the metadata repository.  It is currently a manual process performed by Metadata Curators at NCI, which is currently and will continue to be a bottleneck.  One possible way to streamline the approach is to use a workflow tool out-of-the-box to manage the metadata creation, submission, storage, review, and acceptance.  One such product is Italio, which allows processes to be documented and implemented using BPM.  This would allow Software Engineers and Information Modelers to manage the loading process themselves.

Note: this requirement overlaps with Init1pm5 - Data rollback functionality and Init1pm6 - Automate Loading process

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 Model


  • No labels