# EPAD Stanford ROI and SEG to 3D slicer

**URL:** <https://discourse.slicer.org/t/epad-stanford-roi-and-seg-to-3d-slicer/12609>\
**Category:** Support\
**Created:** [July 18, 2020, 12:08pm UTC](https://discourse.slicer.org/t/epad-stanford-roi-and-seg-to-3d-slicer/12609 "2020-07-18T12:08:40Z")\
**Posts on this page:** 6\
**Page:** 1

<div class="post-metadata">

**Author:** ![Emmanuel\_Salinas\_Mir](https://sea2.discourse-cdn.com/flex002/user_avatar/discourse.slicer.org/emmanuel_salinas_mir/32/6032_2.png) [@Emmanuel\_Salinas\_Mir](https://discourse.slicer.org/u/Emmanuel_Salinas_Mir)\
**Post date:** [July 18, 2020, 12:08pm UTC](https://discourse.slicer.org/t/epad-stanford-roi-and-seg-to-3d-slicer/12609/1 "2020-07-18T12:08:40Z")

</div>

Hi.

Stanford software EPAD saves segmentations and ROIs as .json files.

Is there any possibility of using these files to create a standard nrrd segmentation or labelmap on 3D slicer ?

Regards

---

<div class="post-metadata">

**Author:** ![pieper](https://sea2.discourse-cdn.com/flex002/user_avatar/discourse.slicer.org/pieper/32/8_2.png) [@pieper](https://discourse.slicer.org/u/pieper)\
**Post date:** [July 18, 2020, 2:25pm UTC](https://discourse.slicer.org/t/epad-stanford-roi-and-seg-to-3d-slicer/12609/2 "2020-07-18T14:25:15Z")

</div>

Sure, you should be able to write a simple parser in python and populate Slicer data structures. I don’t think anyone has written code like that, but it would be a great contribution.

---

<div class="post-metadata">

**Author:** ![lassoan](https://sea2.discourse-cdn.com/flex002/user_avatar/discourse.slicer.org/lassoan/32/13_2.png) [@lassoan](https://discourse.slicer.org/u/lassoan)\
**Post date:** [July 18, 2020, 2:43pm UTC](https://discourse.slicer.org/t/epad-stanford-roi-and-seg-to-3d-slicer/12609/3 "2020-07-18T14:43:14Z")

</div>

Here is an example for Osirix ROI importer: [https://github.com/PerkLab/SlicerSandbox/tree/master/ImportOsirixROI](https://github.com/PerkLab/SlicerSandbox/tree/master/ImportOsirixROI)

Since then we have improved Slicer so that you can implement plugin that can load custom file formats right from the “Add data” window. See example here: [https://github.com/SlicerHeart/SlicerHeart/tree/master/TomTecUcdPlugin](https://github.com/SlicerHeart/SlicerHeart/tree/master/TomTecUcdPlugin)

If you are familiar with ePad file format and know a little Python programming then this should be really easy. We can help with mapping data objects to Slicer segmentation or markup nodes.

An alternative approach for ePad would be to move towards standard DICOM structured reports and segmentation objects. AIM made a lot of sense many years ago, when the effort was started, because at that time there was no good way of describing everything in DICOM. Also, AIM started out something that is simpler to use than DICOM. However, DICOM and related software have greatly improved, so now it is hard to justify investing into AIM support and seems to make more sense to converge to DICOM for data sharing and archiving.

---

<div class="post-metadata">

**Author:** ![Emmanuel\_Salinas\_Mir](https://sea2.discourse-cdn.com/flex002/user_avatar/discourse.slicer.org/emmanuel_salinas_mir/32/6032_2.png) [@Emmanuel\_Salinas\_Mir](https://discourse.slicer.org/u/Emmanuel_Salinas_Mir)\
**Post date:** [July 19, 2020, 1:49pm UTC](https://discourse.slicer.org/t/epad-stanford-roi-and-seg-to-3d-slicer/12609/4 "2020-07-19T13:49:29Z")

</div>

Hi @lassoan and @pieper thanks a lot for your kind reply!

We will try the plugins. Unfortunately, we are not that familiar with the ePad file format. But we will try. Hopefully, we will come out with the extension. That might be a nice bridge between ePad, which still attractive by its simple installation, web appearance, and use; and 3D slicer, which has no comparison (Just awesome!).

Regards

---

<div class="post-metadata">

**Author:** ![pieper](https://sea2.discourse-cdn.com/flex002/user_avatar/discourse.slicer.org/pieper/32/8_2.png) [@pieper](https://discourse.slicer.org/u/pieper)\
**Post date:** [July 19, 2020, 2:58pm UTC](https://discourse.slicer.org/t/epad-stanford-roi-and-seg-to-3d-slicer/12609/5 "2020-07-19T14:58:46Z")

</div>

Hi @Emmanuel_Salinas_Mir - we ❤ ePad too, and have [work together](https://projectweek.na-mic.org/PW33_2020_GranCanaria/Projects/ePadSlicer/) on [several](https://github.com/dcmjs-org/dicomweb-server) [projects](https://dicom4qi.readthedocs.io/en/latest/participants/) but never did a native interface.

---

<div class="post-metadata">

**Author:** ![lassoan](https://sea2.discourse-cdn.com/flex002/user_avatar/discourse.slicer.org/lassoan/32/13_2.png) [@lassoan](https://discourse.slicer.org/u/lassoan)\
**Post date:** [July 19, 2020, 5:21pm UTC](https://discourse.slicer.org/t/epad-stanford-roi-and-seg-to-3d-slicer/12609/6 "2020-07-19T17:21:42Z")

</div>

As far as I remember ePad developers have been planning to provide DICOM Segmentation Object and Structured Report import/export features. Before investing too much time into AIM, ask them what is the status of this work. We have intent and funding for improving DICOM Seg and SR import/export in Slicer, so if ePad could use that then you would get full interoperability for free. It would also ensure that your data works with OHIF, Kheops, and many other DICOM compliant software.