Difference between revisions of "CTSC Simon Warfield, CHB"

From NAMIC Wiki
Jump to: navigation, search
Line 36: Line 36:
  
 
=Participants=
 
=Participants=
* PI, clinicians, IT staff, CT investigator, etc
+
* PI: Simon Warfield,  
* staff missing
+
* Co-Investigator: Neil Weisen (confirm)
 +
* Clinicians,  
 +
* IT staff, Laura Alice (confirm)
  
 
=Data=
 
=Data=

Revision as of 15:48, 27 July 2009

Home < CTSC Simon Warfield, CHB

Back to CTSC Imaging Informatics Initiative


Mission

Warfield_ALS_8-year-old-study. Description of big picture, goal(s) of project

Use-Case Goals

We will approach this use-case in three distinct steps, including Basic Data Management, Query Formulation and Processing Support.

Step 1. Basic Data Management.

  • Step 1a. Upload retrospective data
  • Step 1b. Upload new acquisitions as part of data management pipeline

Step 2. Query Formulation

Step 3. Processing Workflow support

Outcome Metrics

Step 1. Data Management

Step 2. Query Formulation

Step 3. Processing Support

Overall

Fundamental Requirements

  • Excellent documentation
  • Example scripts to support custom query, custom schema extensions as required
  • Data should be accessible 24/7
  • Guaranteed redundancy
  • Enough space to grow repository as required

Participants

  • PI: Simon Warfield,
  • Co-Investigator: Neil Weisen (confirm)
  • Clinicians,
  • IT staff, Laura Alice (confirm)

Data

Approximately 30 subjects currently, collection ongoing.

Retrospective data to manage in Step 1a:

  • MR structural (DICOM + NRRD)
  • MR Diffusion (DICOM + NRRD)
  • MR Functional (DICOM + NRRD)
  • Protocol and associated data files (ascii text (.txt) and matlab .mat)

Ongoing acquisition data to manage in Step 1b:

  • EEG
  • Clinical (paper intake, text)
  • Behavioral (paper intake, text)
  • MEG (Record + Photogrmty data, ascii text, European Data Format Plus (.edf))

Workflows

Current Data Management Process

Target Data Management Process (Step 1.)

Target Query Formulation (Step 2.)

Target Processing Workflow (Step 3.)

Other Information