Transcript TRN-0000-14 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
CONFIDENTIAL
TRN-0000-14 Rev 04/17/06
2
Table of Contents
• Terminology
• DICOM Overview
• Summary
CONFIDENTIAL
TRN-0000-14 Rev 04/17/06
3
Terminology
CONFIDENTIAL
TRN-0000-14 Rev 04/17/06
4
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).
CONFIDENTIAL
TRN-0000-14 Rev 04/17/06
5
Terminology
• Service Class – A set of functionality relating to a single type of realworld 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.
CONFIDENTIAL
TRN-0000-14 Rev 04/17/06
6
DICOM Overview
CONFIDENTIAL
TRN-0000-14 Rev 04/17/06
7
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
CONFIDENTIAL
TRN-0000-14 Rev 04/17/06
8
iSite Implementation of the DICOM Information
Model (Simplified)
Patient
has
User
User
Study
contains
User
User
Series
comprised of
User
User
Images
CONFIDENTIAL
TRN-0000-14 Rev 04/17/06
9
The DICOM Communications Protocol Model
Medical Imaging Application
Philips iSite
DICOM Application Message Exchange
ConnectR
Upper Layers
(DICOM)
DICOM
Upper Layer
Protocol
AE Title
Transport Layer
Port
IP
IP Address
Network
Interface Layer
CONFIDENTIAL
Presentation Layer
Session Layer
TCP
Lower Layers
(TCP/IP)
Application Layer
Network Layer
Data - Link Layer
Physical Layer
TRN-0000-14 Rev 04/17/06
HTTP, E-mail
Compression, Encryption
Communication Management
End-to-End Communication
Internetworking
LLC | MAC Ethernet, FDDI
UTP, Fiber, Coax
10
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
CONFIDENTIAL
Image stored
TRN-0000-14 Rev 04/17/06
11
Service-Object Pairs
Service Element
Store
• Verb
Store
Image Object
CT Image
• Noun
Image
SOP Class
Store
• Sentence
store image
SOP Instance
Store John’s CT Image
• specific sentence
store this image
CONFIDENTIAL
TRN-0000-14 Rev 04/17/06
12
Service Classes
Composite Service Classes
Normalized Service Classes
Verification
Patient Management
Storage
Study Management
Query/Retrieve
Results Management
Study Content Notification
Basic Print Management
CONFIDENTIAL
TRN-0000-14 Rev 04/17/06
13
Information Objects
Composite IODs
Normalized IODs
Computed Radiography Image
Image Patient Information
Computed Tomography Image
Image Visit Information
Nuclear Medicine Image
Study Information
Ultrasound Image
Study Component Information
Secondary Capture Image
Results Information
Ultrasound Multi-Frame Image
Interpretation Information
Magnetic Resonance Image
CONFIDENTIAL
TRN-0000-14 Rev 04/17/06
14
Object Definitions
Information Object Definition
Image Types
User
User
User
User
Attribute
CR
CT
MR
NM
Pixel Data
US
CONFIDENTIAL
TRN-0000-14 Rev 04/17/06
15
DICOM Tags Identifying Patient and Study
Data
•
•
•
•
•
•
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
• 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
CONFIDENTIAL
TRN-0000-14 Rev 04/17/06
16
Summary
CONFIDENTIAL
TRN-0000-14 Rev 04/17/06
17
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
CONFIDENTIAL
TRN-0000-14 Rev 04/17/06
18
For assistance, please call customer support at
1-877-328-2808 or 1-877-328-2809
CONFIDENTIAL
TRN-0000-14 Rev 04/17/06
19