Init6pm23 - Brain Tumor in silico study - Pathology and Radiology data models

Date: 

12/18/2009

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

Init6pm23

Originator/Customer's Name:

Joel Saltz - forum post

Originator/Customer's Company:

Emory University

Summary of requirement pre-interview, by Reviewer:

A Brain Tumor in silico use case consists of determining genetic, gene expression and outcome correlates of high resolution nuclear morphometry in the diffuse gliomas and their relation to MR features using Rembardt and TCGA datasets.  This involves integrative analysis involving Pathology, Radiology and molecular data.  The following semantic infrastructure requirements fall out of this use case:

• Specific scientific data elements will be shared amongst collaborators, requiring the need for a way to semantically describe the data.  However, through the course of the study, new data elements will be added and some data elements may change.  Therefore, there is a need for an agile modeling approach that does not require significant effort to modify the information model and register the semantic metadata.  This will greatly facilitate the job of the Information Modeler.
• Data elements are generated using specific algorithms.  There needs to be a way to model the features of the algorithm itself and tie it back to the original data.  One of the features of the algorithm could be the code of the algorithm itself.  It would be ideal if this type of model could be generalized for use in the caBIG analytical community so that Software Engineers can reuse it and Cancer Researchers have access to this data.
• The scientific data elements themselves will describe not only the statistical results, but the scientific methodology used on the specimens.  In some sense, this combines the study design with the results.
• The ultimate result of the scientific use case is to design a classifier that predicts outcome.  It will be necessary to describe the classifier, as well as have that description link back to the data that is used to generate it.  In other words, the provenance of the data must be captured so that Cancer Researchers have access to this information.  A common model would facilitate development of systems by Software Engineers.

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

1. Use Case Template
2. Followup Interview

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

Requirement Type (required)

Analyst's assessement of the most appropriate category/type of requirement (no need to ask interviewee):

• Functional: Fundamental or essential to the product - describes what the product has to do or what processing is needed
  
• Nonfunctional: properties the functions must have such as performance, usability, training or documentation
  
  • Project constraint: schedule or budget constraints
    
  • Design constraint: impose restrictions on how the product must be designed, such as conformant to ISO 11179, utilizes 21090 or is able to work on a particular type of device
    
  • Project driver: business-related forces such as descriptions of stakeholders or purpose of the product/project
    
  • Project issue: conditions that will contribute to the success or failure of the project

ConOp Initiative(s)
Requirements Analyst/Business Analyst

• Select most appropriate initiative: (click for descriptions) 
• Initiative 1 - Distributed, federated metadata repositories and model repositories and operations
• Initiative 2 - Automated generation of metadata from line-of-business artifacts
• Initiative 3 - Rules management and contracts support (behavioral semantics)
• Initiative 4 - Semantics support for W3C service oriented architecture resources
• Initiative 5 - HL7 CTS II/ OMG MIF compliant federated terminology services
• Initiative 6 - Controlled biomedical terminology, ontology and metadata content
• Initiative 7 - Assessment of semantic unification of compositional and derivational models
• Initiative 8 - Other

High Level Use Case Summary)
Requirements Analyst/Business Analyst

Please write a short descriptive narrative use case. 

Use Case Linkage (required)
Business Analyst

Which use case(s) is this requirement linked to?  (should follow Use Case numbering scheme <SemCon Ops Initiative>.<analysts initials><requirement number>.<use case number>, for example Init1dbw1.1, Init1dbw1.2, Init2dbw2.1, 2.2, etc.

Use case Number(s):

Conflicts / Dependencies(required)
Requirements Analyst/ Business Analyst

Are there any conflicts with other requirements / use cases? 

Yes OR No - If yes, what and why?

Next Step (required)
(Requirement Analyst / Business Analyst)

After reviewing the results of the interview, the forum, and all other materials related to this requirement, the analyst should recommend the next step, then attach the Tiny Link (on the Info tab) for this page to the Master List table.

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