1 / 11

Leveraging REST in DICOM: A Comprehensive Approach to Modern Web Services

This document explores the application of REST architectural principles to DICOM web services, highlighting its advantages such as simplicity, wide technology support, and suitability for CRUD operations. It details essential concepts like resource-oriented architecture, addressability, statelessness, and representations. By incorporating specific examples like URIs for studies, series, and instances, it illustrates how REST can enhance data accessibility and usability. Furthermore, it discusses leveraging various MIME types and the significance of linking resources within the DICOM framework.

yasir-simon
Télécharger la présentation

Leveraging REST in DICOM: A Comprehensive Approach to Modern Web Services

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Applying REST to DICOM Chris Hafey Feb 23, 2011

  2. Introduction • Three Types of Web Services • RPC Based (WS*) • REST • REST/RPC Hybrid • Pure REST is a great fit for DICOM • Simple • Wide technology support • Many DICOM use cases are CRUDish

  3. Resource Oriented Architecture • Resources • URIs • Addressability • Statelessness • Representations • Links and Connectedness • Uniform Interface

  4. Resources • Entities • DICOM Modules • Patient • Study • UID Based • Study, Series, Instance • Internals • Image Frame • Algorithms • Render Image • Search • Complex Transactions • Merge Studies

  5. URIs • Entites • Use path to specify where an entity is • E.g – A study • http://server/study/1.2.3.4.5 • Algorithms • Use Path to specify which algorithm/entity to run • Pass algorithm parameters via http query parameters • E.g. – render a sop instance as a JPEG with a specific window center/window width • http://server/study/1.2.3.4.5/series/1.2.3/instance/1.2.3?windowWidth=400&windowCenter=40 • Transactions • Use path to specify transactions • The transaction resource can point to other entities that will be affected

  6. Addressability • Expose interesting aspects of its data set as resources • Allows data to be used in ways not originally anticipated • E.g. exposing individual DICOM Modules to be independently accessed

  7. Statelessness • Each HTTP Request happens in complete isolation • No “session” • Simplifies error conditions • Can send the same web request multiple times without side effects

  8. Representations • Leverage MIME Types • Application/XML • Application/JSON • Application/DICOM • Image/JPEG • Image/PNG • A resource can be returned in multiple representations

  9. Links and Connectedness • Use HREF to link between resources • DICOM Examples • Patient to Study • Study to Series • Series to Instance • Presentation State to Image • Structured report to Image

  10. Uniform Interface

  11. Reference Books • RESTful Web Services • Leonard Richardson & Sam Ruby • RESTful Web Services Cookbook • SubbuAllamaraju • REST in Practice • Ian Robinson, Jim Webber, and SavasParastatidis

More Related