ImageIds

Since cornerstone supports the display of DICOM and non DICOM images stored in archives supporting standard interfaces as well as proprietary, an abstract mechanism is needed to identify images within cornerstone. This abstract mechanism is done by using a URL which cornerstone uses to determine the way in which it will access the image data as well as which image to access. The url scheme specifies the server plugin to use to load the image data. The plugin will use the rest of the URL to actually resolve the image. Note that the contents of the url are completely up to the plugin developer - it could use any identifier it needs to find the image such as UIDs, GUIDs, filenames or database row ids.

A special case exists for WADO based access where the url scheme of http or https is considered a WADO url.

Here are some examples:

WADO

http://www.medical-webservice.st/RetrieveDocument?requestType=WADO&studyUID=1.2.250.1.59.40211.12345678.678910&seriesUID=1.2.250.1.59.40211.789001276.14556172.67789&objectUID=1.2.250.1.59.40211.2678810.87991027.899772.2&contentType=application%2Fdicom&transferSyntax=1.2.840.10008.1.2.4.50

DICOM CGET

dicomcget://pacsarchive:104?studyUid=1.2.250.1.59.40211.12345678.678910&seriesUid=1.2.250.1.59.40211.789001276.14556172.67789&instanceUid=1.2.250.1.59.40211.2678810.87991027.899772.2&frame=0

DICOM CMOVE

dicomcmove://pacsarchive:104?studyUid=1.2.250.1.59.40211.12345678.678910&seriesUid=1.2.250.1.59.40211.789001276.14556172.67789&instanceUid=1.2.250.1.59.40211.2678810.87991027.899772.2&frame=0

Proprietary GUID based

custom1://server?imageId=38120cae-bdcd-4102-b799-c8b9965d3421

Proprietary database rowid based

custom2://server/1353056

Proprietary file based

custom3://server/pathologyimages/12345.jpg