DICOMweb Resources

A fully implemented DICOMweb server (including optional services) exposes the following RESTful resources:

VerbPathDescriptionReference
POST{s}/studiesStore instancesStore Transaction (STOW-RS): 10.5
GET{s}/studies?...Query for studiesSearch Transaction (QIDO-RS): 10.6
GET{s}/studies/{study}Retrieve entire studyRetrieve Transaction (WADO-RS): 10.4
GET{s}/studies/{study}/renderedRetrieve rendered studyRetrieve Transaction (WADO-RS): 10.4
POST{s}/studies/{study}Store instancesStore Transaction (STOW-RS): 10.5
GET{s}/studies/{study}/metadataRetrieve metadataRetrieve Transaction (WADO-RS): 10.4
GET{s}/studies/{study}/series?...Query for series in a studySearch Transaction (QIDO-RS): 10.6
GET{s}/studies/{study}/series/{series}Retrieve entire seriesRetrieve Transaction (WADO-RS): 10.4
GET{s}/studies/{study}/series/{series}/renderedRetrieve rendered seriesRetrieve Transaction (WADO-RS): 10.4
GET{s}/studies/{study}/series/{series}/metadataRetrieve series metadataRetrieve Transaction (WADO-RS): 10.4
GET{s}/studies/{study}/series/{series}/instances?...Query for instances in a seriesSearch Transaction (QIDO-RS): 10.6
GET{s}/studies/{study}/series/{series}/instances/{instance}Retrieve instanceRetrieve Transaction (WADO-RS): 10.4
GET{s}/studies/{study}/series/{series}/instances/{instance}/renderedRetrieve rendered instanceRetrieve Transaction (WADO-RS): 10.4
GET{s}/studies/{study}/series/{series}/instances/{instance}/metadataRetrieve instance metadataRetrieve Transaction (WADO-RS): 10.4
GET{s}/studies/{study}/series/{series}/instances/{instance}/frames/{frames}Retrieve frames in an instanceRetrieve Transaction (WADO-RS): 10.4
GET{s}/{bulkdataURIReference}Retrieve bulk dataRetrieve Transaction (WADO-RS): 10.4
POST{s}/workitems{?AffectedSOPInstanceUID}Create a work itemWorklist Service (UPS-RS): 11
POST{s}/workitems/{instance}{?transaction}Update a work itemWorklist Service (UPS-RS): 11
GET{s}/workitems{?query*}Search for work itemsWorklist Service (UPS-RS): 11
GET{s}/workitems/{instance}Retrieve a work itemWorklist Service (UPS-RS): 11
PUT{s}/workitems/{instance}/stateChange work item stateWorklist Service (UPS-RS): 11
POST{s}/workitems/{instance}/cancelrequestCancel work itemWorklist Service (UPS-RS): 11
POST{s}/workitems/{instance}/subscribers/{AETitle}{?deletionlock}Create subscriptionWorklist Service (UPS-RS): 11
POST{s}/workitems/1.2.840.10008.5.1.4.34.5/Suspend subscriptionWorklist Service (UPS-RS): 11
DELETE{s}/workitems/{instance}/subscribers/{AETitle}Delete subscriptionWorklist Service (UPS-RS): 11
GET{s}/subscribers/{AETitle}Open subscription channelWorklist Service (UPS-RS): 11
N/AN/ASend event reportWorklist Service (UPS-RS): 11
OPTIONS{s}/(any)Get service cabailitiesRetrieve Capabilities Transaction : 6.8

Service Endpoints

The service endpoint is denoted above as {s}. Although the specification does not mandate that DICOMweb services are based on the same service endpoint (as shown above), it is typical of REST services that they are. From a RESTful best practices perspective, the “query” REST actions (that return an array of objects) shares the same root as “retrieve” REST actions.