This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revision | ||
|
connectivity [2022/12/14 14:17] yves [Compare PMA.vue and PMA.studio] |
connectivity [2024/10/11 15:28] (current) chris |
||
|---|---|---|---|
| Line 1: | Line 1: | ||
| ===== Connectivity ===== | ===== Connectivity ===== | ||
| - | We live in a connected world, where vertical data-silos unfortunately are still much to frequent. | + | We live in a connected world, where vertical data-silos unfortunately are still much too frequent. |
| - | With our PMA.vue and PMA.studio products, we want to help you integrate disparate information sources, and bring them together in a single harmonized interface. | + | With our PIMSLS products, we want to help you integrate disparate information sources, and bring them together in a single harmonized interface. |
| - | ==== PMA.vue ==== | + | PIMSLS allows interaction with multiple PMA.core tile servers simultaneously (as well as [[https://free.pathomation.com|PMA.start]] and [[https://my.pathomation.com|My Pathomation]]). |
| - | With PMA.vue, you can integrate virtual slides ([[https://realdata.pathomation.com/what-whole-slide-images-wsis-are-made-of/|find out what makes these data so unique from other imaging data]] from [[https://www.pathomation.com/formats|any number of slide scanners]] into a single user interface. | + | Meta-data is important to describe and annotate data. When configured properly in PMA.core, PIMSLS visualizes these accordingly and can be used as a front-end for interactive data capture from end-users. |
| - | You get tree-based navigation on top of your slide repositories (organized through a single PMA.core back-end [[https://www.youtube.com/watch?v=sepPIexKELE|tile server]]). | + | Speaking of annotations: with PIMSLS you have the option to integrate data-layers and overlays from different image analysis suites. You can [[https://diagnosticpathology.biomedcentral.com/counter/pdf/10.1186/s13000-022-01225-4.pdf|run a proprietary plugin in QuPath and another one in Fiji]], and then visualize both results in PIMSLS to assess which implementation is best suited based on different conditions. |
| - | Not only can you connect to data within your own organization, PMA.vue also makes it easy to reach out to external parties and connect other to //you// in return. PMA.vue offers many sharing features, and comes with built-in snapshot capabilities to prepare manuscripts and other publications. | ||
| - | ==== PMA.studio ==== | + | ==== PIMSLS connectivity ==== |
| - | PMA.studio adds connectivity where PMA.vue stops. | + | The following table gives an overview of just some of the connective capabilities of PIMSLS: |
| - | PMA.studio allows interaction with multiple PMA.core tile servers simultaneously (as well as [[https://free.pathomation.com|PMA.start]] and [[https://my.pathomation.com|My Pathomation]]). | + | ^ Connectivity ^ Functionality ^ PIMSLS ^ |
| - | + | | Incoming | slides stored on server | Yes | | |
| - | Meta-data is important to describe and annotate data. When configured properly in PMA.core, PMA.studio visualizes these accordingly and can be used as a front-end for interactive data capture from end-users. | + | | | slides stored on network drive | Yes | |
| - | + | | | slides stored on S3 storage | Yes | | |
| - | Speaking of annotations: with PMA.studio you have the option to integrate data-layers and overlays from different image analysis suites. You can [[https://diagnosticpathology.biomedcentral.com/counter/pdf/10.1186/s13000-022-01225-4.pdf|run a proprietary plugin in QuPath and another one in Fiji]], and then visualize both results in PMA.studio to assess the conditions which implementation is best suited for what conditions. | + | | | slides stored in [[https://www.azure.com|Azure]] | Yes | |
| - | + | | | slides stored on FTP | Yes | | |
| - | + | | | slides stored local HDD | Yes | | |
| - | ==== Compare PMA.vue and PMA.studio ==== | + | | | slides stored in [[https://my.pathomation.com|My Pathomation]] | Yes | |
| - | + | | | Annotations | Yes | | |
| - | The following table compares connectivity provisions between PMA.vue and PMA.studio: | + | | Layout and presentation | Pre-configured grids | Yes | |
| - | + | | | Tab-based viewport organization | Yes | | |
| - | ^ Connectivity ^ Functionality ^ PMA.vue ^ PMA.studio ^ | + | | | Aribitrary grid sizes | Yes | |
| - | | Incoming | slides stored on server | Yes | Yes | | + | | Outgoing | Share live links to a folder | Yes | |
| - | | | slides stored on network drive| Yes | Yes | | + | | | Share live links to a slide | Yes | |
| - | | | slides stored on S3 storage | Yes | Yes | | + | | | Share live links to regions of interest | Yes | |
| - | | | slides stored in [[https://www.azure.com|Azure]] | Yes | Yes | | + | | | Share live links to grid | Yes | |
| - | | | slides stored on FTP | Yes | Yes | | + | | | Snapshot creation | Yes | |
| - | | | slides stored local HDD | - | Yes | | + | | | Annotations | Yes | |
| - | | | slides stored in [[https://my.pathomation.com|My Pathomation]] | - | Yes | | + | |
| - | | | Annotations | - | Yes | | + | |
| - | | Layout and presentation | Pre-configured grids | Yes | Yes | | + | |
| - | | | Tab-based viewport organization | Yes | Yes | | + | |
| - | | | Aribitrary grid sizes| - | Yes | | + | |
| - | | Outgoing | Share live links to a folder | Yes | Yes | | + | |
| - | | | Share live links to a slide | Yes | Yes | | + | |
| - | | | Share live links to regions of interest | Yes | Yes | | + | |
| - | | | Share live links to grid | Yes | Yes | | + | |
| - | | | Snapshot creation | Yes | Yes | | + | |
| - | | | Annotations | - | Yes | | + | |