auto_slides
Differences
This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revision | ||
|
auto_slides [2025/10/22 23:13] ali |
auto_slides [2025/10/22 23:16] (current) ali |
||
|---|---|---|---|
| Line 30: | Line 30: | ||
| ===== Share administration ===== | ===== Share administration ===== | ||
| - | We’ve worked hard on making the sharing concept in PMA.studio broadly applicable to a variety of content. We’ve also worked on making it easy to share content. | + | We’ve worked hard on making the sharing concept in PIMS LS broadly applicable to a variety of content. We’ve also worked on making it easy to share content. |
| So with all this sharing going on then, it’s only natural to be asking after a while “wait, what am I actually sharing?”. | So with all this sharing going on then, it’s only natural to be asking after a while “wait, what am I actually sharing?”. | ||
| Line 66: | Line 66: | ||
| In order to convince your administration that adding digital pathology to it is a really good idea, you want to upgrade the interface to this: | In order to convince your administration that adding digital pathology to it is a really good idea, you want to upgrade the interface to this: | ||
| - | With PMA.studio, you can now get exactly this effect. | + | With PIMS LS, you can now get exactly this effect. |
| Let’s switch to Jupiter to see how this works: | Let’s switch to Jupiter to see how this works: | ||
| Line 84: | Line 84: | ||
| ===== The PIMS LS API ===== | ===== The PIMS LS API ===== | ||
| - | Ok, we’ve identified our slide. Now let’s go to the PIMS LS. Unfortunately, PMA.python doesn’t have a studio module yet, so we’ll have to interface with the API directly for the time being. | + | Ok, we’ve identified our slide. Now let’s go to the PIMS LS. Unfortunately, PMA.python doesn’t have a PIMS LS module yet, so we’ll have to interface with the API directly for the time being. |
| The back-end call that we need is /API/Share/CreateLinkForSlide and takes on the following parameters: | The back-end call that we need is /API/Share/CreateLinkForSlide and takes on the following parameters: | ||
| Line 126: | Line 126: | ||
| [patient] | [patient] | ||
| - | [case] | + | [case] |
| - | [slides] | + | [slides] |
| | | ||
| Say that we want to offer a case-representation of breast cancer patient 06420637F. We use Share/CreateLinkForFolder and point to a folder instead of a slide: | Say that we want to offer a case-representation of breast cancer patient 06420637F. We use Share/CreateLinkForFolder and point to a folder instead of a slide: | ||
| Line 134: | Line 134: | ||
| {{:automating_folders.png?400|}} | {{:automating_folders.png?400|}} | ||
| - | The result again appears on the PMA.studio side. And clicking on it results in a mini-browser interface: | + | The result again appears on the PIMS LS side. And clicking on it results in a mini-browser interface: |
| {{:automating_folders1.png?400|}} | {{:automating_folders1.png?400|}} | ||
| Line 140: | Line 140: | ||
| ===== What’s next ===== | ===== What’s next ===== | ||
| - | After PMA.core, we’re starting to provide back-end API calls into PMA.studio as well. Even though as we prefer developers to integrate with PMA.UI directly, there are scenarios where automation through PMA.UI makes sense. When you’re in one of the following scenarios when: | + | After PMA.core, we’re starting to provide back-end API calls into PIMS LS as well. Even though as we prefer developers to integrate with PMA.UI directly, there are scenarios where automation through PMA.UI makes sense. When you’re in one of the following scenarios when: |
| * PIMS LS is your main cockpit interface to work with slide content, but there are a few other routes (like an intranet) through which you want to provide quick access to content, too. | * PIMS LS is your main cockpit interface to work with slide content, but there are a few other routes (like an intranet) through which you want to provide quick access to content, too. | ||
| - | * You have an (AP)LI(M)S, PACS, VNA, or other system and you’re in a PoC phase to add digital pathology capabilities to your own platform, PMA.studio automation may be a quicker route to go than adapting our SDKs. | + | * You have an (AP)LI(M)S, PACS, VNA, or other system and you’re in a PoC phase to add digital pathology capabilities to your own platform, PIMS LS automation may be a quicker route to go than adapting our SDKs. |
| - | Do keep in mind however that we’re providing the PMA.studio back-end mostly for convenience, at least for the time being. There are any number of ways in which you may want to integrate digital pathology in your infrastructure and workflows. For a high level of customization, you’re really going to have to move up to PMA.UI, as well as a back-end counterpart like PMA.python, PMA.php, or PMA.java. | + | Do keep in mind however that we’re providing the PIMS LS back-end mostly for convenience, at least for the time being. There are any number of ways in which you may want to integrate digital pathology in your infrastructure and workflows. For a high level of customization, you’re really going to have to move up to PMA.UI, as well as a back-end counterpart like PMA.python, PMA.php, or PMA.java. |
auto_slides.1761163982.txt.gz · Last modified: 2025/10/22 23:13 by ali
