![](media/image1.png){width="9.243055555555555in" height="1.0in"}

+----------+-----------------------------------------------------------+
| ###      | ### Imaging Wo                                            |
|  **MEETI | rkspace Deliverable Review and Strategic Planning Meeting |
| NG INFOR |                                                           |
| MATION** | ### February 4, 2008                                      |
|          |                                                           |
|          | ### 1 PM to 3 PM (ET)                                     |
+----------+-----------------------------------------------------------+
| ##       | ### ![](media/image2.wmf)                                 |
| # **ATTE |                                                           |
| NDEES**  |                                                           |
+----------+-----------------------------------------------------------+
| ### **SU | [*RADLEX RESEARCH PLAYBOOK                                |
| MMARY**  | SUMMARY....                                               |
|          | ......................................................... |
|          | .............2*](#nathan-hall-at-ohio-state-university-an |
|          | d-harvey-maman-in-boston-are-reviewing-pt-and-rt-models.) |
|          |                                                           |
|          | XIP AND XIP CLINICAL RESEARCH HOST                        |
|          | SUMMARY.....                                              |
|          | ........................................................4 |
|          |                                                           |
|          | *OPEN SOURCE VIEWER AND ACRIN USE CASE                    |
|          | RE                                                        |
|          | QUIREMENTS.............................................6* |
|          |                                                           |
|          | *CLINICAL TRAIL TOOL INTEGRATION (CTTI)                   |
|          | REQUIR                                                    |
|          | EMENTS.................................................9* |
|          |                                                           |
|          | ACTION                                                    |
|          | ITEMS..                                                   |
|          | ......................................................... |
|          | ........................................................9 |
|          |                                                           |
|          | [ARTIFACTS.....................                           |
|          | ......................................................... |
|          | ..........................................10](#artifacts) |
|          |                                                           |
|          | ### *RADLEX RESEARCH PLAYBOOK SUMMARY*                    |
|          |                                                           |
|          | ### RadLex is using Google Group to post all              |
|          | documents because it is more user friendly than GForge, b |
|          | ut the GForge repository will have the Google page links. |
|          |                                                           |
|          | ### Curt Langlot                                          |
|          | z gave a review of the last two deliverables (Documentati |
|          | on and Lessons Learned) for the RadLex Playbook project.  |
|          |                                                           |
|          | ### The documentation file for the RadLex Research Play   |
|          | book was reviewed and a brief overview of the RadLex webs |
|          | ite was given. (website link: <http://radlex.org/viewer>) |
|          |                                                           |
|          | ### Key points for the Lessons Learned document           |
|          |                                                           |
|          | ### Consensus is achievable                               |
|          |                                                           |
|          | ### Better term development tools are needed              |
|          |                                                           |
|          | ### Mapping for or                                        |
|          | derable names is needed (there is a high demand for this) |
|          |                                                           |
|          | ### RadLex-EVS harmonization is needed                    |
|          |                                                           |
|          | #                                                         |
|          | ## Some of the original terms for RadLex came from SNOMED |
|          |                                                           |
|          | ### The R                                                 |
|          | adLex project developed 5000 terms and the goal is to hav |
|          | e these harmonized terms inserted into the NCI Thesaurus. |
|          |                                                           |
|          | ### Q: What is the                                        |
|          | timeframe for putting these terms into the NCI Thesaurus? |
|          |                                                           |
|          | ### A: Preliminary mapping would have t                   |
|          | o be done to determine how much overlap exists in order t |
|          | o begin estimating the amount of time this would take. Th |
|          | is will be discussed at the next NCI Thesaurus meeting, a |
|          | nd the group will be notified of the estimated timeframe. |
|          |                                                           |
|          | ### Overlap will probably be                              |
|          |  low, but it depends on what portion is being focused on. |
|          |                                                           |
|          | ### If the RadLex terms are g                             |
|          | oing to be inserted into the NCI Thesaurus, it would be b |
|          | est to put them all in and not choose a specific portion. |
|          |                                                           |
|          | ### Q:                                                    |
|          |  Is it expected that these terms would be used in other i |
|          | maging projects like DICOM ontology, AIM, XIP, NCIA, etc? |
|          |                                                           |
|          | ### A: NCIA intends to incor                              |
|          | porate the RadLex terms and the AIM project is driven by  |
|          | RadLex. RSNA has had success in creating vendor-interest. |
|          |                                                           |
|          | ### Q: Will these terms be put into EVS and be availa     |
|          | ble for all the communities within caBIG, and will this g |
|          | roup be the owners of these terms, providing definitions? |
|          |                                                           |
|          | ### A: Curre                                              |
|          | ntly these terms do not have definitions, but some are in |
|          |  the process of being put in (UML Lex(?)), and the rest o |
|          | f the definitions will be identified and added this year. |
|          |                                                           |
|          | ### The committees who developed these terms k            |
|          | now there is an editorial curation aspect, but these peop |
|          | le would be the point of contact for technical questions. |
|          |                                                           |
|          | ### Paul Mul                                              |
|          | hern volunteered to be the Gatekeeper for questions relat |
|          | ed to this issue, which he will send on to Curt Langlotz. |
|          |                                                           |
|          | ### The CDISC community is enthusiastic to adopt RadLex.  |
|          |                                                           |
|          | ### *XIP AND XIP CLINICAL RESEARCH HOST SUMMARY*          |
|          |                                                           |
|          | ### Lawrence Tarbox gave a r                              |
|          | eview of the Connect-A-Thon. The team did well for their  |
|          | first Connect-A-Thon and XIP did well in a DICOM network. |
|          |                                                           |
|          | ### The f                                                 |
|          | irst year deliverable (XIP Library) wrapped up imaging pr |
|          | ocesses and visualization into an interoperable package.  |
|          |                                                           |
|          | ### Improved version of DICOM was incorporated.           |
|          |                                                           |
|          | ### Provided sorting routines                             |
|          |                                                           |
|          | ### Lawrence Tarbox gave a list of                        |
|          |  functionalities included in the most recent devlierable  |
|          | as well as the functionalities that have yet to be incorp |
|          | orated. Most of the deliverables this year provided a bas |
|          | ic tool, and the follow-on project will be moving towards |
|          |  a full-blown application by building more functionality. |
|          |                                                           |
|          | ### Q: C                                                  |
|          | an you explain more about the remote rendering component? |
|          |                                                           |
|          | ### A: There are two variants, t                          |
|          | he first depends on the remote display client and the ren |
|          | dering where the application is happening. The remote cli |
|          | ent is a web browser and requires a lot of web bandwidth  |
|          | because the image is brought in. The second variant uses  |
|          | java version applet that gets downloaded into the browser |
|          | . It sets up a separate out of bin channel (?) that moves |
|          |  the image. A subsample of the data set is downloaded to  |
|          | render a small volume and a compressed jpg file is sent.  |
|          |                                                           |
|          | ### Q: Is the remote rendering server an XIP application? |
|          |                                                           |
|          | ### A: It's an XIP remote builder (?) It u                |
|          | ses working group 23 host, which is an XIP host. The 23 h |
|          | ost was separated from the application to make it easier. |
|          |                                                           |
|          | ### A demonstration of                                    |
|          |  remote rendering locally should be included in the next  |
|          | Face-to-Face to fully show the remote rendering function. |
|          |                                                           |
|          | ### The system was designed as modularly as possi         |
|          | ble so that it could be used as a standalone or together. |
|          |                                                           |
|          | ### *OPEN SOURCE VIEWER AND ACRIN USE CASE REQUIREMENTS*  |
|          |                                                           |
|          | ### **OPEN SOURCE VIEWER**                                |
|          |                                                           |
|          | ### The Open Source Viewer is part of the X               |
|          | IP tool kit, but can be used separate from XIP. Currently |
|          |  Cedara is used (leased as a proprietary product), but in |
|          |  the spirit of caBIG™, the Open Source Viewer would be de |
|          | veloped as an open source imaging tool to replace Cedara. |
|          |                                                           |
|          | ### Q: The requirements do n                              |
|          | ot address harmonization with existing caBIG standards. I |
|          | s there a need for harmonization requirements with caBIG? |
|          |                                                           |
|          | ### A: No. The viewer will use the AIM library an         |
|          | d AIM tools to create AIM instances and use middleware so |
|          | ftware to store AIM annotations to the AIM Grid services. |
|          |                                                           |
|          | ### Q: How will you capture interoperability?             |
|          |                                                           |
|          | ### A: Just like it uses VTK and ITK, it will use AIM li  |
|          | braries. This is not a grid service, it is a grid client. |
|          |                                                           |
|          | ### Q: Is this tool meant to replace Cedara?              |
|          |                                                           |
|          | ### A: This is part of what                               |
|          | NCI would look for in the responders' proposal. Proposals |
|          |  would most likely address plans to phase out proprietary |
|          |  Cedara requirements and phase in the Open Source Viewer. |
|          |                                                           |
|          | ### Q: Has there been input from NCIA?                    |
|          |                                                           |
|          | ### A: NCIA gave                                          |
|          |  requirements to Cedara and the NCI will consider these r |
|          | equirements in the development of the Open Source Viewer. |
|          |                                                           |
|          | ### The requi                                             |
|          | rements document has a section on incorporating the Open  |
|          | Source Viewer into caGRID. It was previously discussed th |
|          | at this particular section should be taken out because it |
|          |  would be difficult to accomplish in the given timeframe. |
|          |                                                           |
|          | ### The group                                             |
|          | should use the wiki and the Listserv to flesh out details |
|          |  and concerns regarding the RFP and SOW for this project. |
|          |                                                           |
|          | ### It would be helpful to have a formal                  |
|          | requirements document, like a template that would be used |
|          |  consistently for all projects. Find out what NCI uses fo |
|          | r their requirements document and use that as a template. |
|          |                                                           |
|          | ### **ACRIN USE CASE**                                    |
|          |                                                           |
|          | ### Th                                                    |
|          | is project will use an ongoing ACRIN study as a use case. |
|          |                                                           |
|          | ### I                                                     |
|          | tem 3.3.3.5.2, "All images that have associated AIM marku |
|          | ps added to them shall be exported to the ge-ACRIN NCIA i |
|          | nstance and the AIM markup associate shall be preserved." |
|          |                                                           |
|          | ### This item assumes there is an NCIA instance           |
|          |  running at ACRIN. There should be a gACRIN node set up.  |
|          |                                                           |
|          | ### There will either be uploading                        |
|          | of AIM objects via MIRC, or going through the Grid route. |
|          |                                                           |
|          | ### A grid-enabled version at NCIA is dependent           |
|          |  on getting gACRIN completed. A contract has been written |
|          |  to install the grid-enabled version at three institutes. |
|          |                                                           |
|          | ### It                                                    |
|          | may be worth delaying installation and taking the GRID FT |
|          | P dependency out because there will be a better solution. |
|          |                                                           |
|          | ### Q: Ha                                                 |
|          | s the SQL problem with this instance of NCIA been solved? |
|          |                                                           |
|          | ### A: NCIA originally used the ORACLE database, bu       |
|          | t ORACLE is expensive and impractical. The mySQL version  |
|          | is ready to go and will be offered to PTPB (?) and ACRIN. |
|          |                                                           |
|          | ### *CLINICAL TRIAL TOOL INTEGRATION (CTTI) REQUIREMENTS* |
|          |                                                           |
|          | ### Pathology images are stored in                        |
|          | an instance at Wash U and uses a portal designed by Booz  |
|          | Allen Hamilton. It allows the use of images in a querable |
|          |  way to be viewed through the image microscope at Wash U. |
|          |                                                           |
|          | ### The gACRIN project is divided into two co             |
|          | mponents; a grant side and a contract (?) side. It can us |
|          | e caTissue to track pathology images in the Wash U databa |
|          | se. It tracks a sample from source to post test at NCIA.  |
|          |                                                           |
|          | ### The CTTI                                              |
|          | project plans to engage the cooperative groups and to sho |
|          | w that caBIG tools can be integrated in real clinic work. |
|          |                                                           |
|          | ### Nathan Hall at Ohio State University an               |
|          | d Harvey Maman in Boston are reviewing PT and RT models.  |
+----------+-----------------------------------------------------------+
| ###      | -   Paul Mulhern will provide a project update for the    |
| **ACTION |     Middleware.                                           |
|  ITEMS** |                                                           |
|          | -   Paul Mulhern will be the Gatekeeper for questions     |
|          |     regarding RadLex and send them on to Curt Langlotz.   |
|          |                                                           |
|          | -   Lawrence Tarbox will give a demo of the XIP and XIP   |
|          |     Clinical Research Host next Monday (2/11/2008).       |
|          |                                                           |
|          | -   Plan to have a demonstration of the remote rendering  |
|          |     function at the next Imaging Face-to-Face.            |
|          |                                                           |
|          | -   Ashish Sharma will email Fred Prior to clarify        |
|          |     whether the requirements document for the Open Source |
|          |     Viewer should caGRID functionality.                   |
|          |                                                           |
|          | -   Paul Mulhern will take the proposal of having a       |
|          |     formal requirements document for all projects back to |
|          |     the NCI.                                              |
|          |                                                           |
|          | -   Ashish Sharma will email Paul Mulhern regarding the   |
|          |     issues surrounding GRID FTP, who will circulate the   |
|          |     information to Peter Yan and others.                  |
|          |                                                           |
|          | -   Paul Mulhern will keep Ashish Sharma informed about   |
|          |     the contracts to install gACRIN.                      |
|          |                                                           |
|          | -   Paul Mulhern and Brenda Young will meet to discuss    |
|          |     gACRIN                                                |
|          |                                                           |
|          | -   Paul Mulhern will invite David Wu to the Wednesday    |
|          |     meeting with OSU and NCIA team.                       |
|          |                                                           |
|          | -   Paul Mulhern will schedule a demo of the NLST project |
|          |     to the group.                                         |
+----------+-----------------------------------------------------------+
| #        | > ![](media/image3.wmf) ![](media/image4.wmf)             |
| ## **ART | > ![](media/image5.wmf)                                   |
| IFACTS** |                                                           |
|          |                                                           |
| ###      |                                                           |
+----------+-----------------------------------------------------------+

### 

#######