DICOM and Rendered Imaging Services Overview

rs retrieve rendered services n.w
1 / 23
Embed
Share

Explore the decision to create three separate services for retrieving DICOM images, rendered media, and presentation state data. Learn about the conventions, protocols, transaction types, media types, and resource types associated with the retrieval services. Understand the naming formats for different services and transactions in the imaging domain.

  • Imaging
  • DICOM
  • Rendered Media
  • Presentation State
  • Healthcare
rayaanacharya
safwanso Follow

Uploaded on | 2 Views

Download Presentation

Please find below an Image/Link to download the presentation.

The content on the website is provided AS IS for your information and personal use only. It may not be sold, licensed, or shared on other websites without obtaining consent from the author. If you encounter any issues during the download, it is possible that the publisher has removed the file from their server.

You are allowed to download the files provided on this website for personal or commercial use, subject to the condition that they are used lawfully. All files are the property of their respective owners.

Download Presentation

The content on the website is provided AS IS for your information and personal use only. It may not be sold, licensed, or shared on other websites without obtaining consent from the author.

E N D

Presentation Transcript

  1. RS Retrieve Rendered Services

  2. Decision: Make 3 Separate Services Retrieve DICOM Service Resources: Media Type: Only DICOM media types Query: Add deidentify Note: Returns presentation states as dicom objects All current resources query parameters Retrieve Rendered Service Resources: Media Type: Only Rendered media types Query: Add annotate and deidentify ??? query parameters, Add rendering parameters Note: Presentation state series or instances may not be referenced Study, Series, Instance, and Frame List Retrieve Rendered Presentation State Service Resources: study, series = {presentationSeriesUID} , instance = { presentationUID } Media Type: Only Rendered media types Query: Add annotate and deidentify ???? query parameters, Note: Only Study and presentation states (series and instance) Study resource renders all PS series and their instances IHE taxonomy deidentify

  3. Decision: Make 3 Separate Services RS RS Retrieve DICOM Service RS Retrieve Rendered Service RS Retrieve Presentation State Service URI RS Retrieve DICOM Service RS Retrieve Rendered Service RS Retrieve Presentation State Service WS WS Retrieve Imaging Document Set WS Retrieve Rendered Imaging Document Set WS Retrieve Imaging Document Set Metadata

  4. Conventions Protocols: (transport???) URI, WS, RS Transaction Types: retrieve, store, search, create, delete Media Types: DICOM, rendered, presentation state, (metadata, bulkdata) Resource Types: study, study-metadata, series, series-metadata, instance, instance- metadata, frame list, bulkdata

  5. Service Names Format: { protocol } { transaction type } { media class} Example: RS Retrieve DICOM RS Retrieve Rendered RS Retrieve Rendered Presentation State

  6. Transaction Names Format: { protocol } { transaction type } { media class} {resource type} Examples: URI Retrieve DICOM Study-Metadata URI Retrieve Rendered Instance URI Retrieve Presentation State Series RS Retrieve DICOM Study-Metadata RS Retrieve Rendered Instance RS Retrieve Presentation State Series

  7. HTTP Request Messages (general) GET {origin-server} {/service} {/resource} {?query} {version} CRLF {*header-fields} CRLF {payload} CRLF {server} origin-server (domain name or IP addr) {service} path to the service on origin-server {resource} target resource {query}optional and specifies any query parameters {version}required and specifies the HTTP version (HTTP/1.1 or HTTP/2) {headers} required and specifies the header fields {payload} representation of resource

  8. URI Request Messages GET {service} {?query} HTTP/1.1 CRLF {*headers} CRLF CRLF {service} {origin-server} {/path} to the service {?query} {object-id} {general} {rendering} {obsolete} {*headers} required and specifies the header fields {object-id} {general} {rendering} rows , cols , region - rendering service {obsolete} requestType , contentType , transferSyntax , charset studyUID , seriesUID , instanceUID , FrameList - required annotation , anonymization - optional {*headers} Accept , Accept-Charset

  9. RS Request Messages GET {+service} {/resource} {?query} {version} CRLF {*headers} CRLF CRLF make sure service and resource are secure {+service}{origin-server}{/service} path to the service on origin-server {resource} target resource (study, series ) {?query} {general} {rendering} {version} HTTP/1.1 or HTTP/2 {*headers} required and specifies the header fields {general} {rendering} rows , cols , region - rendering service annotation , anonymization - optional {*headers} Accept , Accept-Charset

  10. HTTP Response Message {version} {status-code} {reason-phrase} CRLF {*headers} CRLF {payload} CRLF {version} {status-code} {reason-phrase} {*headers} {payload} HTTP/1.1 or HTTP/2 specifies the meaning of the response text string that has no semantics, Content-Type , Content-Location , Warning, the representation of the requested resource

  11. Documenting a Service Service Request Resource Query Parameters Headers Payload Response Status Codes Headers Payload Media Types - defined by Content-Type response header

  12. Documenting a Protocol Protocol Commonalities Request Service Z Request Resource Query Parameters Headers Payload Response Status Codes Headers Payload Media Types Service A Request Resource Query Parameters Headers Payload Response Status Codes Headers Payload Media Types Resource Query Parameters Headers Payload Response Status Codes Headers Payload Media Types - - -

  13. RS Retrieve Request Commonalities GET {+service} {/resource} {?query} {version} CRLF {*headers} CRLF CRLF {?query} {general} {rendering} Differences RetrieveService Query Media Type DICOM DICOM Rendered {rendering} Rendered Presentation State Rendered

  14. RS Retrieve DICOM Service Resources: study, study-metadata, series, series-metadata, instance, instance- metadata, Frame List, Bulkdata Media Types (DICOM): application/dicom, application/dicom+xml

  15. RS Retrieve Rendered Service Resources: Study, Series, Instance, Frame List Media Types (Rendered): jpeg, jp2, png Rendering Parameters: rows, columns, region, window-level, voilut, preset, quality, order, rotate, flip

  16. RS Retrieve Presentation State Service Resources: study, series, instance Resources Target: presentation series or presentation instance Media Types (Rendered): ????

  17. Service Format Request Resource Query Parameters Fragment Parameters Header Fields Accept Accept-Charset Payload Response Status Code (and Reason Phrase) Header Fields Content-Type Content-Length Payload

  18. HTTP Response Commonalities {version} {status-code} {reason-phrase} CRLF {*headers} CRLF {payload} CRLF {payload} depends on media type and query parameters

  19. Basic Image Review Functionality Layout, Tiling, Selection, Rotation 90 degree increments Flip horizontal Windowing 1stset of VOI LUT or window values in DICOM attributes Presets based on modality Default based on statistical analysis (open issue)of pixel values Zoom and Pan Laterality Overlay Default is to use windowing

  20. Basic Image Review Annotations Laterality? Patient Patient s Name (0010,0010), ??? Issuer of Patient ID (0010,0021) Patient s ID (0010,0020), Patient s Birth Date (0010,0030), Patient s Sex (0010,0040) Study Institution Name (0008,0080) Study ID (0020,0010) ??? Issuer of Accession Number Sequence (0008,0051) Accession Number (0008,0050) (for correlation with study described in the report) (open issues what annotations what should be required

  21. Basic Image Review Series Series Number (0020,0011) (for correlation with series described in the report) Series Description (0008,103E) Acquisition Date Time (0008,002A), if present, else Acquisition Date (0008,0022) and Acquisition Time (0008,0032), if present, else Content Date (0008,0023) and Content Time (0008,0033), if present, else Series Date (0008,0021) and Series Time (0008,0031), if present, else Study Date (0008,0020) and Study Time (0008,0030) Contrast Used Whether or not intravenous contrast was used (C+/-), derived from Contrast/Bolus Agent Sequence (0018,0012), if present, else Contrast/Bolus Agent (0018,0010) Is presentation of images along with report a fundamental use case for rendering

  22. BIR Annotations Image Instance Number (0020,0013) (for correlation with slices described in the report) Slice Location (0020,1041), if present, else Table Position (0018,9327), if present else a value derived from Image Position (Patient) (0020,0032) Slice Thickness (0018,0050) Spacing Between Slices (0018,0088), if present, else a value derived from successive values of Image Position (Patient) (0020,0032) perpendicular to the Image Orientation (Patient) (0020,0037)

  23. BIR Annotations Image (cont) Lossy Compression: Whether or not lossy compression has been applied, derived from Lossy Image Compression (0028,2110), and if so, the value of Lossy Image Compression Ratio (0028,2112) and Lossy Image Compression Method (0028,2114), if present (as per FDA Guidance for the Submission of Premarket Notifications for Medical Image Management Devices, July 27, 2000) Windowing: Currently applied window center and width (or window top and bottom for clamped mode) Given that you have a restful service to retrieve metadata, how badly do you need annotations? 1. Completely unaware browser displaying a URL 2. Highly aware client that can retrieve metadata, and images, but cannot manipulate images

Related


No related presentations.

More Related Content