Difference between revisions of "2014 Summer Project Week: Chronicle"
From NAMIC Wiki
| (One intermediate revision by the same user not shown) | |||
| Line 46: | Line 46: | ||
<div style="width: 27%; float: left; padding-right: 3%;"> | <div style="width: 27%; float: left; padding-right: 3%;"> | ||
<h3>Progress</h3> | <h3>Progress</h3> | ||
| − | * | + | * Held productive discussions with several possible users |
| + | ** MGH for GBM research | ||
| + | ** Childrens/MGH/BWH for RPDR and mi2b2 data management | ||
| + | ** U. Iowa Huntingtons clinical data management | ||
| + | * Did experimental uploads to couchdb server installed in Iowa | ||
| + | ** uploads ongoing (225K instances so far on one server) | ||
| + | ** performance appears to be good even with lots of data | ||
| + | * Reviewed scalability with Jim | ||
</div> | </div> | ||
</div> | </div> | ||
Latest revision as of 14:11, 27 June 2014
Home < 2014 Summer Project Week: Chronicle
Key Investigators
- Steve Pieper, Isomics
- Anyone else who is interested
Project Description
Chronicle is an idea to have a database and processing system based on DICOM and CouchDB. The basic ideas are covered in the Chronicle Pamphlet.
Objective
- Lots of DICOM and related data to be organized for easy access
- Standardized representations
- Distributed replication
- Filtered replication
- Simultaneous access and update
- Automatic triggering of processing modules
- Auto data conversion
- Workflow management
- Access from a variety of tools
- Slicer
- Web Apps
- Batch
Approach, Plan
- Give demos of current work in progress if people are interested
- Discuss
- NoSQL
- JavaScript
- MapReduce for Medical Records
- DICOM, Electronic Medical Records
- HTML5 Apps, WebGL
- SlicerChronicle
Progress
- Held productive discussions with several possible users
- MGH for GBM research
- Childrens/MGH/BWH for RPDR and mi2b2 data management
- U. Iowa Huntingtons clinical data management
- Did experimental uploads to couchdb server installed in Iowa
- uploads ongoing (225K instances so far on one server)
- performance appears to be good even with lots of data
- Reviewed scalability with Jim
