Where communities thrive

  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
  • May 01 16:10
    HusseinKhodadadi closed #16
  • May 01 16:09
    HusseinKhodadadi edited #16
  • Apr 23 04:15
    HusseinKhodadadi edited #16
  • Apr 23 04:14
    HusseinKhodadadi opened #16
  • Apr 09 07:13
    JiangWeian closed #116
  • Mar 17 01:48
    Zaid-Safadi edited #112
  • Mar 17 01:47

    Zaid-Safadi on dicomcloud-pacs


  • Mar 15 03:31
    x9517536607 commented #112
  • Mar 14 04:53
    Zaid-Safadi commented #112
  • Mar 14 04:34

    dependabot[bot] on nuget


  • Mar 14 04:33

    Zaid-Safadi on development

    Bump log4net from 2.0.5 to 2.0.… Merge pull request #114 from DI… (compare)

  • Mar 14 04:33
    Zaid-Safadi closed #114
  • Feb 25 15:35
    Zaid-Safadi commented #116
  • Feb 24 09:08
    JiangWeian commented #116
  • Feb 23 10:09
    JiangWeian opened #116
  • Feb 22 03:23
    JiangWeian closed #115
  • Feb 22 03:03
    Zaid-Safadi commented #115
  • Feb 22 01:43
    JiangWeian commented #115
  • Feb 22 01:42
    JiangWeian edited #115
  • Feb 06 09:01
    JiangWeian opened #115
Thank you for your concern.I will try it after I have free.
I start a webPacs project.The front-end is based on cornerstone.My Server(back-end) is a java httpServer.
The server just return back dicom image as a base64 string.But the speed from server to front-end is slow.
I'm thinking to use dicomCloud as back-end server. But I don't know how dicomcloud solve this problem?
Can anyone help me? @Zaid-Safadi
Zaid Safadi

@zhan2016 the DICOMcloud server is designed for this type of scenario and the DICOMweb-js client also uses cornerstone. Speed won't be a problem as the code is optimized and send the dicom images in their native format (with almost any transferSyntax you pick) with no conversion to base64 needed. Have you tried the instructions on the DICOMcloud project README to run the code locally?

Once you store an image, you can retrieve it directly with a WADO URL such as: https://yourdomain/wadouri?RequestType=wado&studyUID=studyInstanceUID&seriesUID=seriesInstanceUID&objectUID=sopInstanceUID&contentType=application/dicom

Wow,thank you first. I will try it and do some benchmark. Can we use more means to speed up the transfer speed for poor network. Can you advise me some solution, For example, image Layered display? @Zaid-Safadi
Some areas of our customers have a poor Network infrastructure. @Zaid-Safadi
Zaid Safadi
sure @zhan2016 , the code is optimized for streaming as it does all the work necessary on the store. To speed up the transfer, you can configure the store to pre-cache images in any transfers syntax you like so when you request the image for streaming, no transformation is done on the server side. It literally will use the parameters to construct the path of the dicom image and return it to the client. Once you have the server up and running let me know what cases you run into.
ok, Thank you. I will test dicomcloud from today. How to understand pre-cache images? How does this operation speed up transfer? @Zaid-Safadi
Zaid Safadi
@zhan2016 , by default you won't need to do anything, but if you want to see how this feature works, take a look at the StoreCommand here at the end of the file, you will see the StorageSettings class prepopulated with the pre-cached images