DICOM Conformance Statement

Endodigi V1.1
Revision History

Version Date Changes Reason

V1.1 14.04.2023 Whole document Update

V1.1 Page 2
Table of Contents

Revision History ........................................................................................................................ 2

Table of Contents ...................................................................................................................... 3
Definitions, Terms and Abbreviations:....................................................................................... 4
CONFORMANCE STATEMENT OVERVIEW .................................................................................. 5
INTRODUCTION......................................................................................................................... 6
AUDIENCE ............................................................................................................................. 6
REMARKS .............................................................................................................................. 6
NETWORKING ........................................................................................................................... 7
IMPLEMENTION MODEL........................................................................................................ 7
Application Data Flow ....................................................................................................... 7
FUNCTIONAL DEFINITIONS OF AE .......................................................................................... 7
DICOM MODULE OF ENDODIGI SOFTWARE ........................................................................... 7
Sequencing of Real World Activities................................................................................... 7
Modality Worklist Sequence.............................................................................................. 7
Association Establishment Policies ........................................................................................ 8
General Association Policies .............................................................................................. 8
SCU Worklist Specification .................................................................................................... 8
Verify connection with a remote AE Specification ............................................................... 10
MEDIA STORAGE CONFORMACE STATEMENT ......................................................................... 12
IMPLEMENTATION MODEL.................................................................................................. 12
Application Data Flow ..................................................................................................... 12
File Information .................................................................................................................. 13
Common Image Attributes used to generate Image DICOM File ...................................... 13
Image attributes .............................................................................................................. 14
Attributes used to generate Report DICOM File ............................................................... 14
Report attributes ............................................................................................................ 14

V1.1 Page 3
Definitions, Terms and Abbreviations:

Definitions, terms and abbreviations used in this document are defined within the different
parts of the DICOM standard. Abbreviations and terms are as follows:

AE DICOM Application Entity

AET Application Entity Title
ASCE Association Control Service Element
CSE Customer Service Engineer
FSC File-Set Creator
IOD (DICOM) Information Object Definition
ISO International Standard Organization
PDU DICOM Protocol Data Unit
SCU DICOM Service Class User (DICOM client)
SCP DICOM Service Class Provider (DICOM server)
SOP DICOM Service-Object Pair

V1.1 Page 4
CONFORMANCE STATEMENT OVERVIEW

This document is a DICOM conformance statement in accordance with the standard as

specificated in DICOM PS 3.2

The DICOM module for Endodigi Software allow that Endodigi Software act like “Acquisition
Modality” in the use area.

Adquisition Modality is a device that acquires and creates medical images

The enable characteristics will be determinate on the license used to enable the DICOM
module.
Licenses modulus available:
 Export Files License: Allow export images and reports to the specific folder path in
disk.

 Worklist License: Allow realice a query to SCP about Modality Workilist, is included the
Export file license too.

Query Modality Worklist: Based on a query entered at the Acquisition Modality, a modality
worklist is generated listing all the ítems that satisfacy the query, this list of Schedule
Procedure Steps with selected demographic information is returned to the acquisition
Modality

Tabla de servicios En una Red DICOM

SOP Classes Service User (SCU) Service Provider(SCP)
Verifications
Echo YES YES
Workflow Management
Modality Worklist YES NO
Information Model –FIND

Tabla de servicios de almacenamiento en Medios

Media Storage Application Write files (FSC) Read Files (FSR)
Profile
USB Flash Drive, Network Yes No
drive, Local drive

V1.1 Page 5
INTRODUCTION

AUDIENCE
This document is intended for hospital staff health system integrators, software designers and
implementers. It is assumed that the reader has a working understanding of DICOM.

REMARKS
DICOM, by itself does not guarantee interoperability. However, the Confiormace Stament
facilitates first-level validation for interoperability between different application supporting
the same DICOM functionality. This Conformace Statement is not intended to replace
validation with other DICOM equipment to ensure proper exchange of information intended.
The scope of this Conformance Statement is to facilate communication with the Endodigi
Software System and other vendors medical equipement. The conformace Statement should
be read and unsderstand in conjunction with the DICOM standard [DICOM]. However, by itself
it is not guaranteed to ensure the desired interoperability and a successful interconnectivity.
The use should be aware of the following important issues:
 The comparision of different conformance statement is the first step towards
assessing interconnectivity between Endodigi Capture Software y otros.
 Test procedures should be defined to validate the desired level of connectivity
The DICOM standard will evolve to meet the user’s future requeriments. ENDODIGI capture
software reserves the right to make changes to its products or to discontinue its delivery.

V1.1 Page 6
NETWORKING

IMPLEMENTION MODEL
Application Data Flow

The DICOM module of ENdodigi Software can realize the query worklist as SCU and the verification
ECHO SCP/SCU
 Echo verification: In SCU it is done from the configuration screen by pressing the Test button.
Starts the C-ECHO command process, then waits for the response. The result of this command
will be reported with a message on the screen. In SCP the module responds successfully to the
received Echo message.
 Worklist SCU: enables scheduled workflow where the patient and case information parameters
are retrieved from a Worklist Server. The Worklist SCU performs searches using a Modality
Worklist Query.

FUNCTIONAL DEFINITIONS OF AE

DICOM MODULE OF ENDODIGI SOFTWARE

The DICOM module of endodigi software applied when the Endodigi Software is initialized and
the activation process using a license was finalized properly. The endodigi software will be able
to show and enable in a graphical interface the features available according to the module
license purchased.

Sequencing of Real World Activities

Modality Worklist Sequence

V1.1 Page 7
Association Establishment Policies
General Association Policies
The DICOM application Context Name (ACN)
Application Context Name 1.2.840.10008.3.1.1.1

The Maximum Length PDU negotiation is included in all associations establishment request. The
maximum length PDU for an association initiated by Endodigi Dicom software (not configurable) is:
Maximum Length PDU 16384

Number of Associations
Initialize one at time. Not allow multiple associations at same time.
Asynchronus Nature
The module work over one synchronous association.
Implementation Identifying Information
Implementation UID 1.3.6.1.4.1.30071.6

Implementation Version Name mDCM 0.9.0.0.1

SCU Worklist Specification

SOP Classes:
The Dicom module of Endodigi software prove Standard conformance to the following SOP Classes:
SOP Class Name SOP Class UID SCU SCP
Modality worklist information Model – 1.2.840.10008.5.1.4.31 Yes no
FIND

Association Policies
See General Asociation Policies
Association initiation Policiy
The Dicom module of Endodigi software attempts to initiate a new association for the following service
operation:
Query Modality Worklist
Associated Real-world activity- Query worklist of a remote AE
If the user enter to Database, the query to the AE is initalized.

V1.1 Page 8
SOP Presentation Context Table – Query worklist of remote AE
Presentation Context Table
Abstract Syntax Transfer Syntax Role Extended
Name UID Name UID Negotiation
Modality 1.2.840.10008.5.1.4.31 ImplicitVRLittleEndian 1.2.840.10008.1.2 SCU NONE
Worklist
information
Model -
FIND

SOP Specific Conformance Statement – Query Worklist of a remote AE

Endodigi Software Extension establish an association to the remote AE, send the C-FIND
request and close it after receiving the response. It uses the following query in the c-FIND
request:

Name Tag Source Comment

Modality (0008,0060) Filled by User Default query value
can be set from
Setting screen
Patient ID (0010, 0020) Return value
Institution Name (0008, 0080) Return value
Accession Number (0008, 0050) Return value
Admission ID (0038, 0010) Return value
Study Instance UID (0020, 000D) Return value
Patient Name (0010, 0010) Return value
Patients Birth Date (0010, 0030) Return value
Patients Sex (0010, 0040) Return value
Medical Alerts (0010, 2000) Return value
Patients Telecom (0010, 2155) Return value
Information
Patients Telephone (0010, 2154) Return value
Numbers
Persons Telecom (0040, 1104) Return value
Information
Patients Address (0010, 1040) Return value
Patient Comments (0010, 4000) Return value
Reason For The (0040, 1002) Return value
Requested Procedure
Referring Physician (0008, 0090) Return value
Name
Requested Procedure (0032, 1060) Return value
Description
Requested Procedure (0040, 1001) Return value
ID
Requested Procedure (0040, 1003) Return value
Priority
Requesting Physician (0032, 1032) Return value
Scheduled (0040, 0006) Return value
Performing Physician
Name

V1.1 Page 9
Scheduled Procedure (0040, 0002) Return value
Start Date
Scheduled Procedure (0040, 0003) Return value
Start Time
Scheduled Procedure (0040, 0007) Return value
Step Description
Scheduled Procedure (0040, 0009) Return value
Step ID
Scheduled Procedure (0040, 0011) Return value
Step Location
Scheduled Station AE (0040, 0001) Return value
Title
Scheduled Station (0040, 0010) Return value
Name

The following table summarizes the behavior in response to command statuses:

Service Status Further Meaning Error Code Behavior
Success Success 0000H Show success
indicator and display
results
Pending Matching continues FF00H Results are added to
the display
Other Failure Any other status Stop and display
error message

Verify connection with a remote AE Specification

SOP Classes:
Endodigi Dicom extension prove Standard conformance to the following SOP Classes:
SOP Class Name SOP Class UID SCU SCP
Verification SOP Class 1.2.840.10008.1.1 Yes Yes

Association Policies
See General Asociation Policies
Association initiation Policiy
Endodigi Dicom Extension Verification SCU initates an association when user click on Test button in the
configuration screen.
Associated Real-world activity- Echo Opeartion

Associations will be released upon the receipt of each C-ECHO confirmation.

The result of association will be show on a message pop up.
An incoming Verification Request will cause the AE to accept the association and respond with a
Verification Response (SCP)

SOP Presentation Context Table – Verification

Presentation Context Table
Abstract Syntax Transfer Syntax Role Extended
Name UID Name UID Negotiation
Verification 1.2.840.10008.1.1 ImplicitVRLittleEndian 1.2.840.10008.1.2 SCU/SCP NONE
SOP Class

V1.1 Page 10
SOP Specific Conformance Statement for Verification SOP Class
The following table summarizes the behavior in response to command statuses:
Service Status Further Meaning Error Code Behavior
Success Success 0000H Show indicator
Other Failure Any other status Show indicator

V1.1 Page 11
MEDIA STORAGE CONFORMACE STATEMENT

IMPLEMENTATION MODEL

This section of the DICOM conformace statement specifies the Endodigi Software compliance
to DICOM requeriments for media exportation. It is details the DICOM Media Storage
Application and roles that are supported by this product.
Endodigi Software is able to export images and report to DICOM media.

Application Data Flow

Exportation diagram of resources of DICOM module of Endodigi Software:

The Dicom module of Endodigi software can create a file with DICOM Format on the folder
path setting over determinated media disk(USB disk, Local Disk, networkdisk). The default
value location can be changed setting the path from Dicom Configuration screen.

AE Specifications

The DICOM module will create a file using the path setting on Endodigi software

Real world Activity Role

Export Image to Storage Media FSC
Export Report to Storage Media FSC

Activity Export Image/report

The DICOM file created will have the .dcm extension, not customizable
The following Red marks show the button to realize the action Export.
You can export the images to DICOM format using the contextual export button or add by
dragging the images to the export button. When the selection is complete press the Export
button.
In the case of wanting to export the report to DICOM format, you can press the Export report
button

V1.1 Page 12
From Menu Export ovear each image

File Information

SOP class UID: SecondaryCaptureImageStorage 1.2.840.10008.5.1.4.1.1.7

Dicom Transfer Syntax: ExplicitVRLittleEndian 1.2.840.10008.1.2.1
SOP Instance UID: Generated
Each image will be save as .dcm on the explicit location.

Common Image Attributes used to generate Image DICOM File

Name Tag Source Comment
Modality (0008,0060) Visit Data Query Modality
Patient ID (0010, 0020) Patient Data
Institution Name (0008, 0080) Patient Data
Accession Number (0008, 0050) Visit Data Visit folder name
Study Date (0008,0020) Visit Data bcoFecha
Study Time (0008,0030) Visit Data bcoFecha
Study Description (0008.1030) Visit Data
Study Instance UID (0020, 000D) Visit Data Stored from worklist
or generated if not
have any associated
Patient Name (0010, 0010) Patient Data
PatientAge Patient Data
Patients Birth Date (0010, 0030) Patient Data
Patients Sex (0010, 0040) Patient Data
Medical Alerts (0010, 2000) Patient Data
Source Application (0002,0016) Patient Data SCU_AE
Entity Title

V1.1 Page 13
Image attributes
Name Tag Source Comment
Series Instance UID (0020,000E) Generated
ImageComments (0020,4000) Image comment
Series Date (0008,0021) Date creation File

SOP class UID: SecondaryCaptureImageStorage 1.2.840.10008.5.1.4.1.1.7

Dicom Transfer Syntax: ExplicitVRLittleEndian 1.2.840.10008.1.2.1
SOP Instance UID: Generated
The report will be exported as an image, each page from report will be stored as an .dcm file.

Attributes used to generate Report DICOM File

Name Tag Source Comment
Modality (0008,0060) Visit Data Query Modality
Patient ID (0010, 0020) Patient Data
Institution Name (0008, 0080) Patient Data
Accession Number (0008, 0050) Visit Data Visit folder name
Study Date (0008,0020) Visit Data Visit date
Study Time (0008,0030) Visit Data Visit date
Study Description (0008.1030) Visit Data
Study Instance UID (0020, 000D) Visit Data Stored from worklist
Patient Name (0010, 0010) Patient Data
PatientAge Patient Data
Patients Birth Date (0010, 0030) Patient Data
Patients Sex (0010, 0040) Patient Data
Medical Alerts (0010, 2000) Patient Data
Source Application (0002,0016) Patient Data SCU_AE
Entity Title

Report attributes
Name Tag Source Comment
Series Instance UID (0020,000E) Generated
Series Number (0020,0011) Number of page
Series Date (0008,0021) Date creation File All page have the
same date

V1.1 Page 14