# Is there interest in a reader for cardiac electrophysiology electronanatomic maps?

**URL:** <https://discourse.slicer.org/t/is-there-interest-in-a-reader-for-cardiac-electrophysiology-electronanatomic-maps/6356>\
**Category:** Development\
**Created:** [April 1, 2019, 5:48pm UTC](https://discourse.slicer.org/t/is-there-interest-in-a-reader-for-cardiac-electrophysiology-electronanatomic-maps/6356 "2019-04-01T17:48:05Z")\
**Posts on this page:** 20\
**Page:** 1

<div class="post-metadata">

**Author:** ![stephan](https://sea2.discourse-cdn.com/flex002/user_avatar/discourse.slicer.org/stephan/32/2444_2.png) [@stephan](https://discourse.slicer.org/u/stephan)\
**Post date:** [April 1, 2019, 5:48pm UTC](https://discourse.slicer.org/t/is-there-interest-in-a-reader-for-cardiac-electrophysiology-electronanatomic-maps/6356/1 "2019-04-01T17:48:05Z")

</div>

Hi,  
for a research project I developed a python scripted module that reads data exported from cardiac electroanatomic mapping systems (Ensite Velocity, CARTO 3, and Rhythmia) and creates models in Slicer from it (with the electric data as a scalar overlay).  
The code was good enough for what I needed it for, but it is still quite experimental and not ready to be released as it is (e.g. it is not packed/built into an extension but it is rather the raw python file as generated from the Extension Wizard, and no self-test is implemented).  
I was wondering if there are other cardiac electrophysiologists out there who would like to use this functionality in Slicer. If so, I would try to get it to a more release-ready shape as soon as I can find some time to spare. Otherwise it will probably end up further down on the to-do list…

---

<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:** [April 2, 2019, 12:29pm UTC](https://discourse.slicer.org/t/is-there-interest-in-a-reader-for-cardiac-electrophysiology-electronanatomic-maps/6356/2 "2019-04-02T12:29:54Z")

</div>

Hi @stephan - I’m not currently doing anything with cardiac ep, but I can imagine the code you described being very interesting to people in the field even if it’s not completely packaged up. As far as I know there’s no real standard file format, so having file reader code for the various vendor systems could be handing. Maybe you could just publish a github repository with a clear WIP warning in the readme?

-Steve

---

<div class="post-metadata">

**Author:** ![stephan](https://sea2.discourse-cdn.com/flex002/user_avatar/discourse.slicer.org/stephan/32/2444_2.png) [@stephan](https://discourse.slicer.org/u/stephan)\
**Post date:** [April 2, 2019, 2:28pm UTC](https://discourse.slicer.org/t/is-there-interest-in-a-reader-for-cardiac-electrophysiology-electronanatomic-maps/6356/3 "2019-04-02T14:28:28Z")

</div>

Sounds good. I will do that (probably within the next two weeks) and post updates here.

---

<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:** [April 6, 2019, 4:23am UTC](https://discourse.slicer.org/t/is-there-interest-in-a-reader-for-cardiac-electrophysiology-electronanatomic-maps/6356/4 "2019-04-06T04:23:49Z")

</div>

I fully agree with @pieper’s suggestion. Just make the extension public, even if it is not polished yet, to give others a chance to try it, give feedback, etc.

We have collaborators who use Slicer for EP procedures, with CARTO, they would be probably interested.

---

<div class="post-metadata">

**Author:** ![stephan](https://sea2.discourse-cdn.com/flex002/user_avatar/discourse.slicer.org/stephan/32/2444_2.png) [@stephan](https://discourse.slicer.org/u/stephan)\
**Post date:** [April 10, 2019, 5:30pm UTC](https://discourse.slicer.org/t/is-there-interest-in-a-reader-for-cardiac-electrophysiology-electronanatomic-maps/6356/5 "2019-04-10T17:30:45Z")

</div>

It is out there now: [https://github.com/stephan1312/SlicerEAMapReader](https://github.com/stephan1312/SlicerEAMapReader)

---

<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:** [April 10, 2019, 6:21pm UTC](https://discourse.slicer.org/t/is-there-interest-in-a-reader-for-cardiac-electrophysiology-electronanatomic-maps/6356/6 "2019-04-10T18:21:28Z")

</div>

This looks great @stephan 👍

Just a thought, but if you happen to have any sample data sets to post somewhere that would be great too.

---

<div class="post-metadata">

**Author:** ![jcfr](https://sea2.discourse-cdn.com/flex002/user_avatar/discourse.slicer.org/jcfr/32/17825_2.png) [@jcfr](https://discourse.slicer.org/u/jcfr)\
**Post date:** [April 10, 2019, 6:34pm UTC](https://discourse.slicer.org/t/is-there-interest-in-a-reader-for-cardiac-electrophysiology-electronanatomic-maps/6356/7 "2019-04-10T18:34:26Z")

</div>

Ditto

@stephan When you have a chance, could you associate the `3d-slicer-extension` GitHub topic so that it is listed here: [https://github.com/topics/3d-slicer-extension](https://github.com/topics/3d-slicer-extension)

---

<div class="post-metadata">

**Author:** ![stephan](https://sea2.discourse-cdn.com/flex002/user_avatar/discourse.slicer.org/stephan/32/2444_2.png) [@stephan](https://discourse.slicer.org/u/stephan)\
**Post date:** [April 10, 2019, 8:00pm UTC](https://discourse.slicer.org/t/is-there-interest-in-a-reader-for-cardiac-electrophysiology-electronanatomic-maps/6356/8 "2019-04-10T20:00:08Z")

</div>

> [@jcfr](#):
>
> could you associate the `3d-slicer-extension` GitHub topic so that it is listed here

done

> [@pieper](#):
>
> if you happen to have any sample data sets to post somewhere that would be great too

I’ll work on it.

---

<div class="post-metadata">

**Author:** ![mattjolley](https://sea2.discourse-cdn.com/flex002/user_avatar/discourse.slicer.org/mattjolley/32/3953_2.png) [@mattjolley](https://discourse.slicer.org/u/mattjolley)\
**Post date:** [April 10, 2019, 8:58pm UTC](https://discourse.slicer.org/t/is-there-interest-in-a-reader-for-cardiac-electrophysiology-electronanatomic-maps/6356/9 "2019-04-10T20:58:38Z")

</div>

Yes. As noted above we are working in this space as well, but putting images into CARTO.

Being able to get them from CARTO to Slicer would be very helpful.

---

<div class="post-metadata">

**Author:** ![stephan](https://sea2.discourse-cdn.com/flex002/user_avatar/discourse.slicer.org/stephan/32/2444_2.png) [@stephan](https://discourse.slicer.org/u/stephan)\
**Post date:** [April 10, 2019, 9:03pm UTC](https://discourse.slicer.org/t/is-there-interest-in-a-reader-for-cardiac-electrophysiology-electronanatomic-maps/6356/10 "2019-04-10T21:03:59Z")

</div>

Feel free to test it. We worked mostly with Rhythmia, so CARTO and Velocity testing has been more limited. I am looking forward to any feedback and improvements. Let me know if you have any questions.

---

<div class="post-metadata">

**Author:** ![stephan](https://sea2.discourse-cdn.com/flex002/user_avatar/discourse.slicer.org/stephan/32/2444_2.png) [@stephan](https://discourse.slicer.org/u/stephan)\
**Post date:** [November 21, 2019, 8:06pm UTC](https://discourse.slicer.org/t/is-there-interest-in-a-reader-for-cardiac-electrophysiology-electronanatomic-maps/6356/11 "2019-11-21T20:06:34Z")

</div>

Update: Unfortunately, CARTO import is broken. The extension was developed (and limited testing was done) using sample files exported from a CARTO3 v **4** system.  
In the current version (CARTO3 v **6** ) export from the work station has been changed and the interesting data (the triangulated mesh of the map) is no longer being exported.  
It is unclear whether this change is intentional (might not be, since the files which are now missing from the exported data set are still referred to in other parts of the exported data).  
However, preliminary feedback from the manufacturer indicates that they will probably leave it that way.

---

<div class="post-metadata">

**Author:** ![tomasz](https://avatars.discourse-cdn.com/v4/letter/t/dbc845/32.png) [@tomasz](https://discourse.slicer.org/u/tomasz)\
**Post date:** [February 16, 2020, 2:47pm UTC](https://discourse.slicer.org/t/is-there-interest-in-a-reader-for-cardiac-electrophysiology-electronanatomic-maps/6356/12 "2020-02-16T14:47:22Z")

</div>

Hi Stephan,  
My name is Tom. I am an electrophysiology fellow at the International Clinical Research Center (Brno, Czech Republic) and Medical University of Silesia (Katowice, Poland).  
Thank you for your contribution and development of the reader for cardiac EP maps.

We are planning to initiate the radiosurgery clinical study designed for patients with VT. Thus, I am looking for a solution to merge EP maps with CT scans for procedure planning. Thus, I would like to ask if your reader can be used to integrate Ensite Velocity maps with CT.

I will be grateful for the information.

Kind regards,  
Tom

---

<div class="post-metadata">

**Author:** ![stephan](https://sea2.discourse-cdn.com/flex002/user_avatar/discourse.slicer.org/stephan/32/2444_2.png) [@stephan](https://discourse.slicer.org/u/stephan)\
**Post date:** [February 17, 2020, 7:00pm UTC](https://discourse.slicer.org/t/is-there-interest-in-a-reader-for-cardiac-electrophysiology-electronanatomic-maps/6356/13 "2020-02-17T19:00:49Z")

</div>

Hi Tom,  
thank you for your note and for your interest in the EA map reader. The plug-in is being overhauled right now (since some python-related changes in Slicer 4.11 stopped from working properly), so please bear with me for a couple more weeks. In general, Ensite Velocity maps can be read (although testing has been limited so far)  
I’ll let you know when the plug-in is working again. Thank you for your patience.

Stephan

---

<div class="post-metadata">

**Author:** ![tomasz](https://avatars.discourse-cdn.com/v4/letter/t/dbc845/32.png) [@tomasz](https://discourse.slicer.org/u/tomasz)\
**Post date:** [February 17, 2020, 7:17pm UTC](https://discourse.slicer.org/t/is-there-interest-in-a-reader-for-cardiac-electrophysiology-electronanatomic-maps/6356/14 "2020-02-17T19:17:33Z")

</div>

Thank you Stephan. I am looking forward to hearing from you.  
Yours,  
Tomasz

---

<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:** [February 18, 2020, 12:59am UTC](https://discourse.slicer.org/t/is-there-interest-in-a-reader-for-cardiac-electrophysiology-electronanatomic-maps/6356/15 "2020-02-18T00:59:50Z")

</div>

> [@stephan](#):
>
> The plug-in is being overhauled right now (since some python-related changes in Slicer 4.11 stopped from working properly), so please bear with me for a couple more weeks

Let us know if we can help with anything. If you send the repository URL and a test data set then we may be able to fix Python2/3 API differences.

---

<div class="post-metadata">

**Author:** ![Sergio\_Laranjo](https://sea2.discourse-cdn.com/flex002/user_avatar/discourse.slicer.org/sergio_laranjo/32/4167_2.png) [@Sergio\_Laranjo](https://discourse.slicer.org/u/Sergio_Laranjo)\
**Post date:** [May 15, 2020, 11:33am UTC](https://discourse.slicer.org/t/is-there-interest-in-a-reader-for-cardiac-electrophysiology-electronanatomic-maps/6356/16 "2020-05-15T11:33:08Z")

</div>

Dear Stephan,

Would very much appreciated to have access to the EA map reader, in particular for NavX maps.

Are you planning to share it again?

---

<div class="post-metadata">

**Author:** ![stephan](https://sea2.discourse-cdn.com/flex002/user_avatar/discourse.slicer.org/stephan/32/2444_2.png) [@stephan](https://discourse.slicer.org/u/stephan)\
**Post date:** [June 15, 2020, 8:49am UTC](https://discourse.slicer.org/t/is-there-interest-in-a-reader-for-cardiac-electrophysiology-electronanatomic-maps/6356/17 "2020-06-15T08:49:11Z")

</div>

@Sergio_Laranjo @tomasz

We debugged the reader to make it work with Slicer 4.11 / Python 3.  
Also, an accompanying publication has been submitted and is currently under review.  
The extension can be found at

> **[stephan1312/SlicerEAMapReader](https://github.com/stephan1312/SlicerEAMapreader/)**
>
> Read cardiac electrophysiology maps from various electroanatomic mapping systems into 3D Slicer - stephan1312/SlicerEAMapReader

  
Just download the [EAMapReader-Slicer-4.11.zip](https://github.com/stephan1312/SlicerEAMapReader/raw/master/EAMapReader-Slicer-4.11.zip) file and install the extension from file.

Also, see the [Readme file](https://github.com/stephan1312/SlicerEAMapReader/blob/master/README.txt)

---

<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:** [June 16, 2020, 5:13am UTC](https://discourse.slicer.org/t/is-there-interest-in-a-reader-for-cardiac-electrophysiology-electronanatomic-maps/6356/18 "2020-06-16T05:13:48Z")

</div>

Thank you for sharing this. Would you consider polishing up this module a bit and submitting to the extension manager? We could also distribute this module as part of SlicerHeart extension, thereby saving some administration and maintenance efforts.

---

<div class="post-metadata">

**Author:** ![Predrag\_Stojadinovic](https://sea2.discourse-cdn.com/flex002/user_avatar/discourse.slicer.org/predrag_stojadinovic/32/8508_2.png) [@Predrag\_Stojadinovic](https://discourse.slicer.org/u/Predrag_Stojadinovic)\
**Post date:** [October 19, 2020, 9:33pm UTC](https://discourse.slicer.org/t/is-there-interest-in-a-reader-for-cardiac-electrophysiology-electronanatomic-maps/6356/19 "2020-10-19T21:33:04Z")

</div>

Hi. This extension is not working. At least not on my Mac.  
This is a notification.

Failed to copy directory /Applications/Slicer.app/Contents/Extensions-29402/EAMapReader/EAMapReader-Slicer-4.11/Slicer.app/Contents/Extensions-29402/EAMapReader into directory /Applications/Slicer.app/Contents/Extensions-29402/EAMapReader-XXXXXX

Do you have any sugestion.

Thank you, very much.

---

<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:** [October 20, 2020, 12:25am UTC](https://discourse.slicer.org/t/is-there-interest-in-a-reader-for-cardiac-electrophysiology-electronanatomic-maps/6356/20 "2020-10-20T00:25:04Z")

</div>

It seems that you missed the installation step of dragging the Slicer application to your Applications folder. See [https://slicer.readthedocs.io/en/latest/user\_guide/getting\_started.html#mac](https://slicer.readthedocs.io/en/latest/user_guide/getting_started.html#mac).

[Next page](https://discourse.slicer.org/t/is-there-interest-in-a-reader-for-cardiac-electrophysiology-electronanatomic-maps/6356.md?page=2)