1 / 20

DICOM Overview

DICOM Overview. Learning Objectives . Describe “DICOM” Describe the fundamentals of the DICOM Model as implemented in Philips iSite PACS Understand basic DICOM interoperability via Service-Object Pair Classes. Table of Contents. Terminology DICOM Overview Summary. Terminology.

december
Download Presentation

DICOM Overview

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. DICOM Overview

  2. Learning Objectives • Describe “DICOM” • Describe the fundamentals of the DICOM Model as implemented in Philips iSite PACS • Understand basic DICOM interoperability via Service-Object Pair Classes

  3. Table of Contents • Terminology • DICOM Overview • Summary

  4. Terminology

  5. Terminology • DICOM Message Service Element (DIMSE) – The set of DICOM Application Layer communication services • Information Object Definition (IOD) – A data abstraction of a class of real-world objects. A collection of related attributes (data elements).

  6. Terminology • Service Class – A set of functionality relating to a single type of real-world activity. Composed of a set of SOP Classes and rules as well as associated semantics. • Service-Object Pair (SOP Class) – The fundamental unit of DICOM functionality. Composed of an IOD and a set of DIMSE services and restrictions or extensions of the IOD.

  7. DICOM Overview

  8. DICOM Overview • Digital Imaging and Communications in Medicine • DICOM is the predominant communication standard between imaging equipment throughout the Healthcare Enterprise • DICOM has an Object-Oriented Design • DICOM utilizes an Entity-Relationship Model • DICOM is a client-server based protocol

  9. iSite Implementation of the DICOM Information Model (Simplified) Patient has User User User User Study Series contains comprised of User User Images

  10. The DICOM Communications Protocol Model Medical Imaging Application Philips iSite DICOM Application Message Exchange ConnectR DICOM Upper Layer Protocol AE Title Application Layer HTTP, E-mail Upper Layers (DICOM) Presentation Layer Compression, Encryption Session Layer Communication Management TCP Port Transport Layer End-to-End Communication IP IP Address Network Layer Internetworking Lower Layers (TCP/IP) Network Interface Layer Data - Link Layer LLC | MAC Ethernet, FDDI Physical Layer UTP, Fiber, Coax

  11. Client-Server Relationship • “Application Entities” (referred to by “AE Title”) negotiate associations to ensure that a shared syntax (language) is available • “Application Entities” have assigned roles such as Service Class Provider and Service Class User Service Request User Provider Response Store this image Image stored

  12. Service Element Verb Image Object Noun SOP Class Sentence SOP Instance specific sentence Store Store CT Image Image Store store image Store John’s CT Image store this image Service-Object Pairs

  13. Service Classes

  14. Information Objects

  15. Object Definitions Information Object Definition Image Types User CR User User User Attribute CT MR Pixel Data NM US

  16. 0010,0010 = Patient Name 0010,0020 = MRN 0010,0030 = DOB 0010,0040 = Sex 0020,000d = Study UID 0020,000e = Series UID 0008,0020 = Date of Study 0008,0030 = Time of Study 0008,0050 = Accession # 0008,0060 = Modality Type AETITLE = AE_Title 0008,103e = Series Description DICOM Tags Identifying Patient and Study Data • These elements are sent in the study data message and are the most common DICOM elements used to verify that the data identified by the customer exists in the source and target interface system pairs as well as in the data message

  17. Summary

  18. Summary • DICOM is a complex standard, but basic message protocol is straightforward • Many Philips iSite features and functions rely upon the presence and proper formatting of specific DICOM elements • When troubleshooting, remember that most issues are typical networking (TCP/IP) issues or improper (unusual) workflow • When questions arise, eliminate networking issues then review the Philips iSite DICOM Conformance Statement for interoperability

  19. For assistance, please call customer support at 1-877-328-2808 or 1-877-328-2809

More Related