Breast Ring-array Ultrasound Imaging System

COCOLY＊DICOM Conformance Statement
Software Version 1.4.0*COCOLY is a certified medical device only applicable in Japan.

LS00-M00005
Revision 00
2021/06/07©2021 Lily MedTech Inc.
Unauthorized reproduction prohibited.

COCOLY DICOM Conformance Statement

LS00-M00005 Rev.00

Trademarks
COCOLY is a registered trademark of Lily MedTech Inc.
DICOM® is the registered trademark of the National Electrical Manufacturers Association.
This document may include trademarks or registered trademarks of other companies.

Notice
The contents of this document are subject to change without prior notice without our legal
obligation. Please refer to the Lily MedTech website for the latest version.
URL https://www.lilymedtech.com/product/cocoly/dicom/

Lily MedTech Inc.

2 / 38LS00-M00005 Rev.00

COCOLY DICOM Conformance Statement

CONFORMANCE STATEMENT OVERVIEW
Breast Ring-array Ultrasound Imaging System COCOLY acquires the ultrasound data andreconstructs the slice and volume images to provide diagnostic images. It downloads worklists
from information systems and save these images to network storage using the Digital Imaging
and Communications in Medicine system, DICOM.
Table 1.1-1 provides an overview of the network services supported by COCOLY.
Table 1.1-1
NETWORK SERVICES
User of Service

Provider of Service

(SCU)

(SCP)

US Image Storage

Yes

No

CT Image Storage

Yes

No

Yes

No

SOP Classes
Transfer

Workflow Management
Modality Worklist Information Model – Find

Lily MedTech Inc.

3 / 38

COCOLY DICOM Conformance Statement

LS00-M00005 Rev.00

Table of Contents
1. INTRODUCTION .................................................................................................. 7
1.1.

AUDIENCE .............................................................................................................. 7

1.2.

REMARKS ............................................................................................................... 7

1.3.

TERMS AND DEFINITIONS ........................................................................................ 8

1.4.

ABBREVIATIONS ................................................................................................... 10

1.5.

REFERENCES ........................................................................................................ 10

2. NETWORKING ................................................................................................... 11
2.1.

IMPLEMENTATION MODEL ...................................................................................... 11

2.1.1.

Application Data Flow ....................................................................................... 11

2.1.2.

Functional Definition of AE’s .............................................................................. 12
Functional Definition of Storage Application Entity ......................................... 12
Functional Definition of Workflow Application Entity ....................................... 12

2.1.3.
2.2.

Sequencing of Real World Activities .................................................................... 12

AE SPECIFICATIONS .............................................................................................. 13

2.2.1.

Verification SCU AE .......................................................................................... 13
SOP Classes .............................................................................................. 13
Association Policies .................................................................................... 13

2.2.1.2.1.

General ............................................................................................... 13

2.2.1.2.2.

Number of Associations ......................................................................... 13

2.2.1.2.3.

Asynchronous Nature ............................................................................ 13

2.2.1.2.4.

Asynchronous Nature ............................................................................ 13

2.2.1.2.5.

Implementation Identifying Information .................................................. 13

Association Initiation Policy ......................................................................... 14
2.2.1.3.1.

Activity – Send Echo ............................................................................. 14

2.2.1.3.1.1.

Description and Sequencing of Activities ............................................ 14

2.2.1.3.1.2.

Proposed Presentation Contexts ....................................................... 14

2.2.1.3.1.3.

SOP Specific Conformance for Verification SOP Classes ........................ 15

Association Acceptance Policy ..................................................................... 15
2.2.2.

Storage SCU AE............................................................................................... 16
SOP Classes .............................................................................................. 16
Association Policies .................................................................................... 16

2.2.2.2.1.

General ............................................................................................... 16

2.2.2.2.2.

Number of Associations ......................................................................... 16

2.2.2.2.3.

Asynchronous Nature ............................................................................ 16

2.2.2.2.4.

Implementation Identifying Information .................................................. 17

Association Initiation Policy ......................................................................... 17
2.2.2.3.1.

Activity – Send Images ......................................................................... 17

2.2.2.3.1.1.

Lily MedTech Inc.

Description and Sequencing of Activities ............................................ 17

4 / 38

COCOLY DICOM Conformance Statement

LS00-M00005 Rev.00

2.2.2.3.1.2.

Proposed Presentation Contexts ....................................................... 18

2.2.2.3.1.3.

SOP Specific Conformance for Storage SOP Classes ............................. 18

Association Acceptance Policy ..................................................................... 19
2.2.3.

MWL SCU AE................................................................................................... 20
SOP Classes .............................................................................................. 20
Association Policies .................................................................................... 20

2.2.3.2.1.

General ............................................................................................... 20

2.2.3.2.2.

Number of Associations ......................................................................... 20

2.2.3.2.3.

Asynchronous Nature ............................................................................ 20

2.2.3.2.4.

Implementation Identifying Information .................................................. 20

Association Initiation Policy ......................................................................... 21
2.2.3.3.1.

Activity –Query Worklist ........................................................................ 21

2.2.3.3.1.1.

Description and Sequencing of Activities ............................................ 21

2.2.3.3.1.2.

Proposed Presentation Contexts ....................................................... 22

2.2.3.3.1.3.

SOP Specific Conformance for MWL SOP Classes ................................. 23

Association Acceptance Policy ..................................................................... 25
2.3.

NETWORK INTERFACES .......................................................................................... 26

2.3.1.

Physical Network Interface ............................................................................... 26

2.3.2.

Additional Protocols ......................................................................................... 26

2.3.3.

IPv4 and IPv6 Support ..................................................................................... 26

2.4.

CONFIGURATION ................................................................................................... 26

2.4.1.

AE Title/Presentation Address Mapping .............................................................. 26
Local AE Titles ........................................................................................... 26
Remote AE Title/Presentation Address Mapping ............................................. 26

2.4.2.

Parameters ..................................................................................................... 27

3. SUPPORT OF CHARACTER SETS .......................................................................... 28
4. SECURTIY ......................................................................................................... 28
5. ANNEXES .......................................................................................................... 29
5.1.

IOD CONTENTS ..................................................................................................... 29

5.1.1.

Created SOP Instances ..................................................................................... 29
CT Image IOD ........................................................................................... 30
Ultrasound Image IOD ............................................................................... 31
Common Modules ...................................................................................... 32
CT Image Module ...................................................................................... 37
US Image Module ...................................................................................... 37

5.2.

DATA DICTIONARY OF PRIVATE ATTRIBUTES ............................................................ 38

5.3.

CODED TERMINOLOGY AND TEMPLATES................................................................... 38

5.4.

GRAYSCALE IMAGE CONSISTENCY ........................................................................... 38

5.5.

STANDARD EXTENDED / SPECIALIZED / PRIVATE SOP CLASSES .................................. 38

Lily MedTech Inc.

5 / 38

COCOLY DICOM Conformance Statement
5.6.

LS00-M00005 Rev.00

PRIVATE TRANSFER SYNTAXES ............................................................................... 38

Lily MedTech Inc.

6 / 38

COCOLY DICOM Conformance Statement

LS00-M00005 Rev.00

1. INTRODUCTION
1.1. AUDIENCEThis document is written for the people that need to understand how COCOLY will integrate into
their healthcare facility. This includes both those responsible for overall imaging network policy
and architecture, as well as integrators who need to have a detailed understanding of the DICOM
features of the product. Integrators are expected to fully understand all the DICOM terminology,
how the tables in this document relate to the product’s functionality, and how that functionality
integrates with other devices that support compatible DICOM features.

1.2. REMARKSThe scope of this DICOM Conformance Statement is to facilitate integration between COCOLY
and other DICOM products. The Conformance Statement should be read and understood in
conjunction with the DICOM Standard. DICOM by itself does not guarantee interoperability.
This Conformance Statement is not supposed to replace validation with other DICOM equipment
to ensure proper exchange of intended information.
The user should be aware of the following important issues:- The comparison of different Conformance Statements is just the first step towards
assessing interconnectivity and interoperability between the product and other DICOM
conformant equipment.
- Test procedures should be defined and executed to validate the required level ofinteroperability with specific compatible DICOM equipment, as established by thehealthcare facility.

Lily MedTech Inc.

7 / 38

COCOLY DICOM Conformance Statement

LS00-M00005 Rev.00

1.3. TERMS AND DEFINITIONS
Informal definitions are provided for the following terms used in this Conformance Statement.
The DICOM Standard is the authoritative source for formal definitions of these terms.
Abstract Syntax – the information agreed to be exchanged between applications,generally equivalent to a Service/Object Pair (SOP) Class. Examples: Verification SOPClass, Modality Worklist Information Model Find SOP Class.
Application Entity (AE) – an end point of a DICOM information exchange, including the
DICOM network or media interface software; i.e., the software that sends or receives
DICOM information objects or messages. A single device may have multiple Application
Entities.
Application Entity Title – the externally known name of an Application Entity, used to
identify a DICOM application to other DICOM applications on the network.
Application Context – the specification of the type of communication used between
Application Entities. Example: DICOM network protocol.
Association – a network communication channel set up between Application Entities.
Attribute – a unit of information in an object definition; a data element identified by atag. The information may be a complex data structure (Sequence), itself composed oflower level data elements. Examples: Patient ID (0010,0020), Accession Number(0008,0050), Photometric Interpretation (0028,0004), Procedure Code Sequence(0008,1032).
COCOLY – The breast ring-array ultrasound imaging system of this conformance.
Information Object Definition (IOD) – the specified set of Attributes that comprise atype of data object; does not represent a specific instance of the data object, but rather
a class of similar data objects that have the same properties. The Attributes may be
specified as Mandatory (Type 1), Required but possibly unknown (Type 2), or Optional(Type 3), and there may be conditions associated with the use of an Attribute (Types 1Cand 2C). Examples: SC Image IOD.
Module – a set of Attributes within an Information Object Definition that are logicallyrelated to each other. Example: Patient Module includes Patient Name, Patient ID, Patient
Birth Date, and Patient Sex.
Lily MedTech Inc.

8 / 38

COCOLY DICOM Conformance Statement

LS00-M00005 Rev.00

Negotiation – first phase of Association establishment that allows Application Entities toagree on the types of data to be exchanged and how that data will be encoded.
Presentation Context – the set of DICOM network services used over an Association,
as negotiated between Application Entities; includes Abstract Syntaxes and Transfer
Syntaxes.
Protocol Data Unit (PDU) – a packet (piece) of a DICOM message sent across the
network. Devices must specify the maximum size packet they can receive for DICOM
messages.
Security Profile – a set of mechanisms, such as encryption, user authentication, or
digital signatures, used by an Application Entity to ensure confidentiality, integrity,
and/or availability of exchanged DICOM data
Service Class Provider (SCP) – role of an Application Entity that provides a DICOM
network service; typically, a server that performs operations requested by another
Application Entity (Service Class User). Examples: Picture Archiving and Communication
System (image storage SCP, and image query/retrieve SCP), Radiology Information
System (modality worklist SCP).
Service Class User (SCU) – role of an Application Entity that uses a DICOM network
service; typically, a client. Examples: imaging modality (image storage SCU, andmodality worklist SCU), imaging workstation (image query/retrieve SCU)
Service/Object Pair (SOP) Class – the specification of the network or media transfer(service) of a particular type of data (object); the fundamental unit of DICOM
interoperability specification. Examples: Ultrasound Image Storage Service, Basic
Grayscale Print Management.
Service/Object Pair (SOP) Instance – an information object; a specific occurrence of
information exchanged in a SOP Class. Examples: a specific x-ray image.
Tag – a 32-bit identifier for a data element, represented as a pair of four digit
hexadecimal numbers, the “group” and the “element”. If the “group” number is odd, thetag is for a private (manufacturer-specific) data element. Examples: (0010,0020)[Patient ID], (07FE,0010) [Pixel Data], (0019,0210) [private data element]
Lily MedTech Inc.

9 / 38

COCOLY DICOM Conformance Statement

LS00-M00005 Rev.00

Transfer Syntax – the encoding used for exchange of DICOM information objects andmessages.
Unique Identifier (UID) – a globally unique “dotted decimal” string that identifies a
specific object or a class of objects; an ISO-8824 Object Identifier. Examples: Study
Instance UID, SOP Class UID, SOP Instance UID.
Value Representation (VR) – the format type of an individual DICOM data element,such as text, an integer, a person’s name, or a code. DICOM information objects can betransmitted with either explicit identification of the type of each data element (Explicit
VR), or without explicit identification (Implicit VR); with Implicit VR, the receiving
application must use a DICOM data dictionary to look up the format of each data element.

1.4. ABBREVIATIONSAEApplication Entity

CT

Computed Tomography

DICOM

Digital Imaging and Communications in Medicine

HIS

Hospital Information System

IOD

Information Object Definition

IPv4

Internet Protocol version 4

IPv6Internet Protocol version 6

ISOInternational Organization for Standards

MWL

Modality Worklist

PACS

Picture Archiving and Communication System

PDU

Protocol Data Unit

RISRadiology Information System.

SCP

Service Class Provider

SCU

Service Class User

SOP

Service-Object Pair

TCP/IP

Transmission Control Protocol/Internet Protocol

US

UltrasoundVR

Value Representation

1.5. REFERENCES
NEMA PS3 Digital Imaging and Communications in Medicine (DICOM) Standard, available free
at https://www.dicomstandard.org/

Lily MedTech Inc.

10 / 38

LS00-M00005 Rev.00

COCOLY DICOM Conformance Statement

2. NETWORKING
2.1. IMPLEMENTATION MODEL2.1.1.Application Data Flow

Echo

Verification
SCU AE

Remote AE
Responds to
Echo

Query
Worklist

MWL SCU AE

Remote AE
ProvidesWorklist Items

Send
ImagesStorage SCU AE

Remote AE
Receives Images

DICOM Standard Interface
Figure 2.1-1
APPLICATION DATA FLOW DIAGRAM- The Verification SCU AE sends a verification request to a remote AE.
In order to verify DICOM connection, C-Echo is issued to remote AE by executing theverify operation via service tool.
- The MWL SCU AE receives Worklist information from a remote AE.
Worklist information is acquired from Remote AE by executing the worklist operation in
COCOLY.
- The Storage SCU AE sends images to a remote AE.
Images are transmitted to Remote AE by executing image transmission operation in
COCOLY.

Lily MedTech Inc.

11 / 38

LS00-M00005 Rev.00

COCOLY DICOM Conformance Statement

2.1.2.Functional Definition of AE’s
Functional Definition of Storage Application Entity
When the image transmission operation is executed in COCOLY, Storage AE creates an IOD
based on the image data, imaging information, and order information acquired by MWL (in thecase of an independently issued inspection, the order information acquired by MWL does notexist, so COCOLY has Issue the required value), and starts image transfer.
Functional Definition of Workflow Application Entity
When the worklist operation is executed in COCOLY, Workflow AE crates an IOD based on the
search conditions specified on the screen and the set search conditions, and C-FIND is executedfor Remote AE.

2.1.3.Sequencing of Real World Activities
StorageAE

Department
Scheduler

WorkflowAE

Image
Server

1. Query Worklist
2. Receive Worklist

3. Select work item

4. Acquire image data
5. Send Acquired Images

Figure 2.1-1
SEQUENCING CONSTRAINTS
Under normal scheduled workflow conditions the sequencing constraints illustrated in above
Figure apply:
1. Query Worklist
2. Receive Worklist
3. Select work item from the Worklist
4. Acquire image data
5. Send Acquired images

Lily MedTech Inc.

12 / 38

LS00-M00005 Rev.00

COCOLY DICOM Conformance Statement

2.2. AE SPECIFICATIONS
2.2.1.Verification SCU AE
SOP Classes
The Verification SCU AE provides Standard Conformance to the following SOP Classes:
Table 2.2-1
SOP CLASS FOR AE VERIFICARIONSOP Classes
Verification SOP ClassSOP Class UID
1.2.840.10008.1.1

SCU

SCP

Yes

No

Association Policies
2.2.1.2.1.

GeneralThe DICOM standard application context name for DICOM 3.0 is always proposed:
Table 2.2-2
DICOM APPLICATION CONTEXT FOR AE VERIFICARION
Application Context Name
2.2.1.2.2.

1.2.840.10008.3.1.1.1

Number of Associations

The Verification SCU AE initiates one Association at a time.
Table 2.2-3
NUMBER OF ASSOCIATIONS INITIATED FOR AE VERIFICARION
Maximum number of simultaneous Association
2.2.1.2.3.

1

Asynchronous Nature

The Verification SCU AE does not support asynchronous mode.
2.2.1.2.4.

Asynchronous Nature

The Verification SCU AE does not support asynchronous mode.
2.2.1.2.5.

Implementation Identifying Information

The implementation information for this Application Entity is:
Table 2.2-4
DICOM IMPLEMENTATION CLASS AND VERSION FOR AE MWL
Implementation Class UID

1.2.392.200339.10339.1.1.4.0

Implementation Version Name

COCOLY_1.4.0

Lily MedTech Inc.

13 / 38

LS00-M00005 Rev.00

COCOLY DICOM Conformance Statement
Association Initiation Policy
2.2.1.3.1.

Activity – Send Echo

2.2.1.3.1.1. Description and Sequencing of Activities
By executing the verification operation in COCOLY, Verification SCU AE starts a new association
for requesting C-Echo to Remote AE.
RemoteVerification SCPAEVerification SCU
AE
1. Open Association
2. C-Echo Request (Verification)
3. Close Association

Figure 2.2-11
SEQUENCING OF ACTIVITY – SEND ECHOA possible sequence of interactions between the Verification AE and a Verification SCP AE (e.g.
image server or department scheduler device) is illustrated in above Figure:1. The Verification SCU AE opens a new association with the Remote AE.
2. The Verification SCU AE sends C-Echo request to the Remote AE and the Remote AE
replies with a C-ECHO response (status success).
3. The Verification SCU AE closes the association with the Remote AE.

2.2.1.3.1.2. Proposed Presentation Contexts
The Verification SCU AE supports the Presentation Contexts shown in the following table.
Table 2.2-5
PROPOSED PRESENTATION CONTEXTS FOR ACTIVITY SEND ECHO
Presentation Context Table
Abstract Syntax
Name
Verification
Lily MedTech Inc.

UID

Transfer Syntax
Name List

UID List

1.2.840.10008

Implicit VR

1.2.840.10008

1.1

Little Endian

.1.2

Role
SCU

Ext.
Neg.
None
14 / 38

LS00-M00005 Rev.00

COCOLY DICOM Conformance Statement

2.2.1.3.1.3. SOP Specific Conformance for Verification SOP Classes
The behavior of Verification SCU AE when encountering status codes in a C-ECHO response issummarized in the Table below:
Table 2.2-6
VERIFICATION C-ECHO RESPONSE STATUS HANDLING BEHAVIOR
Service

Error

Further Meaning

StatusBehavior

Code

Success

Success

0000

Status is displayed.

**

Any other status codes.

Use A-RELEASE torelease the association.
The error information isrecorded in the log andthe error information isdisplayed.

The behavior of Verification SCU AE during communication failure is summarized in the Table
below:
Table 2.2-7
STORAGE COMMUNICATION FAILURE BEHAVIOR
Exception

Behavior

Timeout

The connection is disconnected.

Association aborted by the SCP or network layers

The error information is recorded in
the log and the error information isdisplayed.

Association Acceptance Policy
The Verification SCU AE does not accept Associations.

Lily MedTech Inc.

15 / 38

LS00-M00005 Rev.00

COCOLY DICOM Conformance Statement

2.2.2.Storage SCU AE
SOP Classes
The Storage SCU AE provides Standard Conformance to the following SOP Classes:
Table 2.2-8
SOP CLASS FOR AE STORAGE
SOP Classes

SOP Class UID

SCU

SCP

CT Image Storage

1.2.840.10008.5.1.4.1.1.2

Yes

No

Ultrasound Image Storage

1.2.840.10008.5.1.4.1.1.6.1

Yes

No

Association Policies
2.2.2.2.1.

GeneralThe DICOM standard application context name for DICOM 3.0 is always proposed:
Table 2.2-9
DICOM APPLICATION CONTEXT FOR AE STORAGE
Application Context Name
2.2.2.2.2.

1.2.840.10008.3.1.1.1

Number of Associations

The Storage SCU AE initiates one Association at a time for each destination to which a transfer
request is being processed in the active job queue list. Only one job will be active at a time, theother remains pending until the active job is completed or failed.
Table 2.2-10
NUMBER OF ASSOCIATIONS INITIATED FOR AE STORAGE
Maximum number of simultaneous Association
2.2.2.2.3.

1

Asynchronous Nature

The Storage SCU AE does not support asynchronous mode.

Lily MedTech Inc.

16 / 38

LS00-M00005 Rev.00

COCOLY DICOM Conformance Statement
2.2.2.2.4.

Implementation Identifying Information

The implementation information for this Application Entity is:
Table 2.2-11
DICOM IMPLEMENTATION CLASS AND VERSION FOR AE STORAGE
Implementation Class UID

1.2.392.200339.10339.1.1.4.0

Implementation Version Name

COCOLY_1.4.0

Association Initiation Policy
2.2.2.3.1.

Activity – Send Images

2.2.2.3.1.1. Description and Sequencing of Activities
By executing the image transmission operation in COCOLY, Storage SCU AE starts a newassociation for requesting C-STORE to Remote AE.
Storage SCU AE

Image Server
1. Open Association
2. C-STORE (CT Image/Ultrasound Image)
3. Close Association

Figure 2.2-21
SEQUENCING OF ACTIVITY – SEND IMAGES
A possible sequence of interactions between the Storage AE and an Image Server (e.g. a storage
or archive device supporting Storage SOP Classes as an SCP) is illustrated in above Figure:4. The Storage SCU AE opens a new association with the Image Server.
5. Acquired images are transmitted to the Image Server using a C-STORE request and theImage Server replies with a C-STORE response (status success).
6. The Storage SCU AE closes the association with the Image Server.

Lily MedTech Inc.

17 / 38

LS00-M00005 Rev.00

COCOLY DICOM Conformance Statement
2.2.2.3.1.2. Proposed Presentation Contexts

The Storage SCU AE will propose the Presentation Contexts shown in the following table.
Table 2.2-12
PROPOSED PRESENTATION CONTEXTS FOR ACTIVITY SEND IMAGES
Presentation Context Table
Abstract Syntax
Name

UID

Transfer Syntax
Name List

UID List

1.2.840.10008

Implicit VR

1.2.840.10008

5.1.4.1.1.2

Little Endian.1.2

Ultrasound Image

1.2.840.10008

Implicit VR

1.2.840.10008

Storage

5.1.4.1.1.6.1

Little Endian.1.2

CT Image Storage

Role

Ext.
Neg.

SCU

None

SCU

None

2.2.2.3.1.3. SOP Specific Conformance for Storage SOP Classes
The behavior of Storage SCU AE when encountering status codes in a Storage C-STORE
response is summarized in the Table below:
Table 2.2-13
STORAGE C-STORE RESPONSE STATUS HANDLING BEHAVIOR
Service
StatusSuccess

Error

Further Meaning
SuccessCode0000

Behavior
End the transmission ofimage data.

RefusedOut of Resources

A700-A7FF

Use A-RELEASE to

Error

Data Set does not

A900-A9FF

release the association.
The error information ismatch SOP Class
Error

Cannot Understand

C000-CFFF

recorded in the log andWarning

Coercion of DataB000

the error information isdisplayed.

Elements
Warning

Data Set does not

B007

match SOP Class
WarningElements Discarded

B006

*

*

Any other status codes.

Lily MedTech Inc.

18 / 38

LS00-M00005 Rev.00

COCOLY DICOM Conformance Statement

The behavior of Storage SCU AE during communication failure is summarized in the Table below:
Table 2.2-14
STORAGE COMMUNICATION FAILURE BEHAVIOR
Exception

Behavior

Timeout

The connection is disconnected.

Association aborted by the SCP or network layers

The error information is recorded in
the log and the error information isdisplayed.

Association Acceptance Policy
The Storage SCU AE does not accept Associations.

Lily MedTech Inc.

19 / 38

LS00-M00005 Rev.00

COCOLY DICOM Conformance Statement

2.2.3.MWL SCU AE
SOP Classes
The MWL SCU AE provides Standard Conformance to the following SOP Classes:
Table 2.2-15
SOP CLASS FOR AE MWLSOP Classes
Modality Worklist
Information Model - FIND

SOP Class UID

SCU

SCP

1.2.840.10008.5.1.4.31

Yes

No

Association Policies
2.2.3.2.1.

GeneralThe DICOM standard application context name for DICOM 3.0 is always proposed:
Table 2.2-16
DICOM APPLICATION CONTEXT FOR AE MWL
Application Context Name
2.2.3.2.2.

1.2.840.10008.3.1.1.1

Number of Associations

The MWL SCU AE initiates one Association at a time for a.
Table 2.2-17
NUMBER OF ASSOCIATIONS INITIATED FOR AE MWL
Maximum number of simultaneous Association
2.2.3.2.3.

1

Asynchronous Nature

The MWL SCU AE does not support asynchronous mode.
2.2.3.2.4.

Implementation Identifying Information

The implementation information for this Application Entity is:
Table 2.2-18
DICOM IMPLEMENTATION CLASS AND VERSION FOR AE MWL
Implementation Class UID

1.2.392.200339.10339.1.1.4.0

Implementation Version Name

COCOLY_1.4.0

Lily MedTech Inc.

20 / 38

LS00-M00005 Rev.00

COCOLY DICOM Conformance Statement
Association Initiation Policy
2.2.3.3.1.

Activity –Query Worklist

2.2.3.3.1.1. Description and Sequencing of Activities
By executing the worklist operation in COCOLY, MWL SCU AE starts a new association forrequesting C-FIND to Remote AE.
Worklist search conditions are created based on the values set on the screen and the values set
in the configuration file.

MWL SCU AE

Department Scheduler

1. Open Association
2. C-FIND Request (Worklist Query)

3. C-FIND Response (Worklist Item) – Status - Pending
4. C-FIND Response (Worklist Item) – Status - Pending
5. C-FIND Response – Status - Success
6. Close Association

Figure 2.2-3
SEQUENCING OF ACTIVITY – QUERY WORKLISTA possible sequence of interactions between the MWM SCU AE and a Department Scheduler(e.g. a device such as a RIS which supports the Modality Worklist SOP Class as an SCP) is
illustrated in above Figure:

Lily MedTech Inc.

21 / 38

LS00-M00005 Rev.00

COCOLY DICOM Conformance Statement

1. The MWM SCU AE opens an association with the Department Scheduler.
2. The MWM SCU AE sends a C-FIND request to the Department Scheduler containing theWorklist Query attributes.
3. The Department Scheduler returns a C-FIND response containing the requested
attributes of the first matching Worklist Item.
4. The Department Scheduler returns another C-FIND response containing the requested
attributes of the second matching Worklist Item.
5. The Department Scheduler returns another C-FIND response with status Successindicating that no further matching Worklist Items exist. This example assumes that only
2 Worklist items match the Worklist Query.
6. The MWM SCU AE closes the association with the Department Scheduler.
2.2.3.3.1.2. Proposed Presentation Contexts
The Storage SCU AE is capable of proposing the Presentation Contexts shown in the following
table.
Table 2.2-19
PROPOSED PRESENTATION CONTEXTS FOR ACTIVITY WORKLIST UPDATE
Presentation Context Table
Abstract Syntax
Name
Modality Worklist
Information Model FIND

Lily MedTech Inc.

Transfer Syntax
UID

Name List

UID List

1.2.840.10008.

Implicit VR

1.2.840.10008.

5.1.4.31

Little Endian

1.2

Role

SCU

Ext.
Neg.
None

22 / 38

LS00-M00005 Rev.00

COCOLY DICOM Conformance Statement
2.2.3.3.1.3. SOP Specific Conformance for MWL SOP Classes

The behavior of MWL SCU AE when encountering status codes in a Modality Worklist C-FIND
response is summarized in the Table below:
Table 2.2-20
MODALITY WORKLIST C-FIND RESPONSE STATUS HANDLING BEHAVIOR
Service

Further Meaning

StatusSuccess

Success

Error Code0000

Behavior
Finish getting the worklist.
Display the contents of theacquired work list.

RefusedOut of Resources

A700-A7FF

Release the association

Error

Data Set does not

A900-A9FF

using A-RELEASE.
The error information ismatch SOP Class
Error

Cannot Understand

C000-CFFF

recorded in the log and theWarning

Coercion of Data

B000

error information isdisplayed.

Elements
Warning

Data Set does not

B007

match SOP Class
WarningElements Discarded

B006

*

*

Any other status codes.

The behavior of MWL SCU AE during communication failure is summarized in the Table below:
Table 2.2-21
MODALITY WORKLIST COMMUNICATION FAILURE BEHAVIOR
Exception

Behavior

Timeout

Disconnect the connection.

Association aborted by the SCP or network layers

The error information is recorded in
the log and the error information isdisplayed.

Acquired images will always use the Study Instance UID specified for the Scheduled Procedure
Step (if available). If an acquisition is unscheduled, a Study Instance UID will be generated
locally.
The Table below provides a description of the MWL SCU AE Worklist Request Identifier andspecifies the attributes that are copied into the images. Unexpected attributes returned in a CFIND response are ignored.

Lily MedTech Inc.

23 / 38

LS00-M00005 Rev.00

COCOLY DICOM Conformance Statement
Table 2.2-22
WORKLIST REQUEST IDENTIFIER
Attribute Name

Tag

VR

M

R

D

Scheduled Procedure Step Sequence(0040,0100)

SQ>Modality(0008,0060)

CS

S

x

>Scheduled Station AE Title(0040,0001)

AE

S

x

>Scheduled Procedure Step Start Date

(0040,0002)

DA

S

x

>Scheduled Procedure Step Start Time(0040,0003)

TM> Scheduled Performing Physician's Name

(0040,0006)

PN>Scheduled Procedure Step Description(0040,0007)

LO

x>Scheduled Procedure Step ID(0040,0009)

SH

x

Study Instance UID(0020,000D)

UIx

Requested Procedure Description(0032,1060)

LOx

Requested Procedure ID(0040,1001)

SHx

Accession Number(0008,0050)

SH

x

x

Requesting Physician(0032,1032)

PN

x

x

Requesting Service(0032,1033)

LO

x

x

(0038,0400)

LO

x

Patient's Name

(0010,0010)

PN

x

Patient ID(0010,0020)

LO

Patient's Birth Date

(0010,0030)

DAx

Patient's Sex(0010,0040)

CS

x

Patient's Size

(0010,1020)

DS

x

Patient's Weight(0010,1030)

DSx

Patient Comments(0010,4000)

LTx

Medical Alerts(0010,2000)

LOx

Pregnancy Status(0010,21C0)

USxSpecial Needs(0038,0050)

LOx

Patient State(0038,0500)

LOx

Scheduled Procedure Step Module
x

x
*

x

Requested Procedure Modulex

Imaging Service Request Module

Visit Status Module
Patient's Institution Residence
Patient Identification ModuleSxx

Patient Demographic Modulex

Patient Medical Module

The above table should be read as follows:

Lily MedTech Inc.

24 / 38COCOLY DICOM Conformance Statement

LS00-M00005 Rev.00

Attribute Name : Attributes supported to build this product Worklist Request Identifier.
Tag:

DICOM tag for this attribute.

VR:

DICOM VR for this attribute.

M:

Matching keys for (automatic) Worklist Update. A "S" will indicate that MWL SCU
AE will supply an attribute value for Single Value Matching, a “R” will indicate
Range Matching and a “*” will denote wildcard matching.

R:

Return keys. An "x" will indicate that MWL SCU AE will supply this attribute as
Return Key with zero length for Universal Matching.

D:

Displayed keys. An “x” indicates that this worklist attribute is displayed to the user
during a patient registration dialog. For example, Patient Name will be displayedwhen registering the patient prior to an examination.

Association Acceptance Policy
The MWL SCU AE does not accept Associations.

Lily MedTech Inc.

25 / 38

LS00-M00005 Rev.00

COCOLY DICOM Conformance Statement

2.3. NETWORK INTERFACES
2.3.1.Physical Network Interface
COCOLY is indifferent to the physical medium over which TCP/IP is used.

2.3.2.Additional Protocols
None.

2.3.3.IPv4 and IPv6 Support
COCOLY only supports IPv4 connections.

2.4. CONFIGURATION
2.4.1.AE Title/Presentation Address Mapping
Local AE Titles
The AE Title of local applications is configured by editing the setup file. The AE Titles must be
configured during installation.
Table 2.4-1
AE TITLE CONFIGURATION TABLE
Application Entity

Default AE Title

Default TCP/IP Port

Storage SCU

No Default

Not Applicable

MWL SCUNo Default

Not Applicable

Remote AE Title/Presentation Address Mapping
The AE Title, IP address and port numbers of remote applications are configured by editing the
setup file.

Lily MedTech Inc.

26 / 38

LS00-M00005 Rev.00

COCOLY DICOM Conformance Statement

2.4.2.Parameters
A large number of parameters related to the acquisition and general operation can be configured
by editing the setup file. The Table below only shows those configuration parameters relevant
to DICOM communication. See the Product’s Service Manual for details on general configuration
capabilities.
Table 2.4-2
CONFIGURATION PARAMETERS TABLE

Configurable

Parameter(Yes/No)

Default Value

General Parameter
Supported Transfer Syntaxes

No

Implicit VR Little
EndianMaximum number of simultaneously initiated

No

1

Yes

30s

Yes

30s

Yes

30s

Yes

65536 Bytes

Associations
Storage SCU Parameters
Time-out waiting for an acceptance or rejection
response to an Association Request (Application Level
Timeout)
Time-out waiting for response to a P-DATA-TF(Application Level Timeout)
Time-out waiting for a response to an Association
release request (Application Level Timeout)
Max PDU Send Size

(64KB)
MWM SCU Parameters
Time-out waiting for an acceptance or rejection

Yes

30s

Yes

30s

Yes

30s

Yes

65536 Bytes

response to an Association Request (Application Level
Timeout)
Time-out waiting for response to a P-DATA-TF(Application Level Timeout)
Time-out waiting for a response to an Association
release request (Application Level Timeout)
Max PDU Send Size

(64KB)

Lily MedTech Inc.

27 / 38COCOLY DICOM Conformance Statement

LS00-M00005 Rev.00

3. SUPPORT OF CHARACTER SETS
COCOLY supports the following character sets in addition to the default character sets.
・ISO 2022 IR 87

4. SECURTIYCOCOLY does not support any defined DICOM security profiles.
It is assumed that the product is used within a secured environment. It is assumed that asecured environment includes at a minimum:
a. Firewall or router protections to ensure that only approved external hosts have network
access to the product.
b. Firewall or router protections to ensure that the product only has network access toapproved external hosts and services.
Other network security procedures such as automated intrusion detection may be appropriate
in some environments. Additional security features may be established by the local security
policy and are beyond the scope of this conformance statement.

Lily MedTech Inc.

28 / 38COCOLY DICOM Conformance Statement

LS00-M00005 Rev.00

5. ANNEXES
5.1. IOD CONTENTS
5.1.1.Created SOP Instances
Table 5.1-1 specifies the attributes of a CT Image transmitted by the Storage SCU AE.
Table 5.1-2 specifies the attributes of a US Image transmitted by the Storage SCU AE.
The following tables use a number of abbreviations.
The abbreviations used in the “Presence of …” column are:
VNAP

Value Not Always Present (attribute sent zero length if no value is present)

ANAP

Attribute Not Always Present

ALWAYS

Always Present

EMPTY

Attribute is sent without a value

The abbreviations used in the “Source” column:
MWL

the attribute value source Modality Worklist

USER

the attribute value source is from User input

AUTO

the attribute value is generated automatically

CONFIG

the attribute value source is a configurable parameter

Lily MedTech Inc.

29 / 38

LS00-M00005 Rev.00

COCOLY DICOM Conformance Statement
CT Image IOD

COCOLY provides the CT Image IOD option only for Storage SCU AE, because it does not use
X-ray.
The CT Image IOD consists of the modules of the following table and Additional Attribute as
extended module. The Additional Attribute are described in Table 5.1-13.
Table 5.1-1
IOD OF CREATE CT Image SOP INSTANCES
IE
Patient

ModuleReference

Presenceof Value

Patient

Table 5.1-3

ALWAYS

Clinical Trial SubjectNA

Not Present

General Study

Table 5.1-4

ALWAYS

Patient Study

Table 5.1-5

ALWAYS

Clinical Trial StudyNA

Not Present

General Series

Table 5.1-6

ALWAYS

Clinical Trial SeriesNA

Not Present

Frame of Reference

Table 5.1-7

ALWAYS

SynchronizationNA

Not Present

Equipment

General Equipment

Table 5.1-8

ALWAYS

Image

General Image

Table 5.1-9

ALWAYS

General ReferenceNA

Not Present

Image Plane

Table 5.1-10

ALWAYS

Image Pixel

Table 5.1-11

ALWAYS

Contrast/Bolus

NA

Not Present

DeviceNA

Not Present

SpecimenNA

Not Present

CT Image

Table 5.1-14

ALWAYS

Multi-energy CT ImageNA

Not Present

Overlay PlaneNA

Not Present

VOI LUTNA

Not Present

SOP Common

Table 5.1-12

ALWAYS

Common Instance ReferenceNA

Not Present

Study

SeriesFrame of Reference

Lily MedTech Inc.

30 / 38

LS00-M00005 Rev.00

COCOLY DICOM Conformance Statement
Ultrasound Image IOD

The Ultrasound Image IOD consists of the modules of the following table, plus Image Plane
Module and Additional Attribute as extended module.
The Image Plane Module are described in Table 5.1-10.
The Additional Attribute are described in Table 5.1-13.
Table 5.1-2
IOD OF CREATE Ultrasound Image SOP INSTANCES
IE
Patient

ModuleReference

Presenceof Value

Patient

Table 5.1-3

ALWAYS

Clinical Trial SubjectNA

Not Present

General Study

Table 5.1-4

ALWAYS

Patient Study

Table 5.1-5

ALWAYS

Clinical Trial StudyNA

Not Present

General Series

Table 5.1-6

ALWAYS

Clinical Trial SeriesNA

Not Present

Frame of Reference

Table 5.1-7

ALWAYS

SynchronizationNA

Not Present

Equipment

General Equipment

Table 5.1-8

ALWAYS

Image

General Image

Table 5.1-9

ALWAYS

General ReferenceNA

Not Present

Image Pixel

Table 5.1-11

ALWAYS

Contrast/Bolus

NA

Not Present

Palette Color Lookup TableNA

Not Present

SpecimenNA

Not Present

US Region CalibrationNA

Not Present

US Image

Table 5.1-15

ALWAYS

Overlay PlaneNA

Not Present

VOI LUTNA

Not Present

ICC ProfileNA

Not Present

SOP Common

Table 5.1-12

ALWAYS

Common Instance ReferenceNA

Not Present

Study

SeriesFrame of Reference

Lily MedTech Inc.

31 / 38

LS00-M00005 Rev.00

COCOLY DICOM Conformance Statement
Common Modules
Table 5.1-3
PATIENT MODULE OF CREATED SOP INSTANCES
Attribute Name

Tag

VR

Value

Presence

Sourceof Value
Patient’s Name

(0010,0010)

PN

ALWAYSMWL/
USER

Patient ID(0010,0020)

LO

ALWAYSMWL/
USER

Patient’s Birth Date

(0010,0030)

DA

ALWAYSMWL/
USER

Patient’s Sex(0010,0040)

CS

VNAP

MWL/
USER

Patient Comments(0010,4000)

LT

ANAP

MWL

Table 5.1-4
GENERAL STUDY MODULE OF CREATED SOP INSTANCES
Attribute Name

Tag

VR

Value

Presence

Sourceof Value
Study Instance UID(0020,000D)UIALWAYS

MWL/
AUTO

Study Date

(0008,0020)

DA

VNAP

AUTO

Study Time

(0008,0030)

TM

VNAP

AUTO

Study ID

(0020,0010)

SH

VNAP

AUTO

Accession Number(0008,0050)

SH

VNAP

MWL

Referring Physician's(0008,0090)

PN

VNAP

MWL

(0008,1030)

LO

ANAP

USER

Name
Study Description

Lily MedTech Inc.

32 / 38

LS00-M00005 Rev.00

COCOLY DICOM Conformance Statement
Table 5.1-5

PATIENT STUDY MODULE OF CREATED SOP INSTANCES
Attribute Name

Tag

VR

Value

Presence

Sourceof Value
Patient's Age(0010,1010)

AS

ANAP

MWL/
USER

Patient's Size

(0010,1020)

DS

ANAP

MWL

Patient's Weight(0010,1030)

DS

ANAP

MWL

Table 5.1-6
GENERAL SERIES MODULE OF CREATED SOP INSTANCES
Attribute Name

Tag

VR

Value

Presence

Sourceof Value
Modality(0008,0060)

CS

“CT”

ALWAYS

AUTO

for CT Image IOD.
“US”
for US Image IOD
Series Instance UID(0020,000E)

UI

ALWAYS

AUTO

Series Number(0020,0011)

IS

ALWAYS

AUTO

Laterality(0020,0060)

CS

ALWAYS

USER

Series Date

(0008,0021)

DA

ALWAYS

AUTO

Series Time

(0008,0031)

TM

ALWAYS

AUTO

Series Description(0008,103E)

LO

ALWAYS

USER/

Laterality
description and user

AUTO

input.
Operators' Name

(0008,1070)

PN

Body Part Examined(0018,0015)

CS

Patient Position(0018,5100)

CS

Lily MedTech Inc.

ALWAYSUSER“BREAST”

ALWAYS

AUTO

“HFP”

ALWAYS

AUTO

33 / 38

LS00-M00005 Rev.00

COCOLY DICOM Conformance Statement
Table 5.1-7

FRAME OF REFERENCE MODULE OF CREATED SOP INSTANCES
Attribute Name

Tag

VR

Value

Presence

Sourceof Value
Frame of Reference(0020,0052)

UI

ALWAYS

AUTO(0020,1040)

LO

EMPTY

AUTO

UID
Position Reference
Indicator
Table 5.1-8
GENERAL EQUIPMENT MODULE OF CREATED SOP INSTANCES
Attribute Name

Tag

VR

Value

Presence

Sourceof Value
Manufacturer(0008,0070)

LO

Institution Name

(0008,0080)

Station Name
Institutional“Lily MedTech Inc.”

ALWAYS

AUTO

LO

ANAP

CONFIG(0008,1010)

SH

ANAP

CONFIG(0008,1040)

LO

ANAP

CONFIG(0008,1090)

LO

ALWAYSCONFIG

Device Serial Number(0018,1000)

LO

ALWAYSCONFIG

Software Versions(0018,1020)

LO

ALWAYSCONFIG

Department Name
Manufacturer's Model
Name

Table 5.1-9
GENERAL IMAGE MODULE OF CREATED SOP INSTANCES
Attribute Name

Tag

VR

Value

Presence

Sourceof Value
Instance Number(0020,0013)

IS

Patient Orientation(0020,0020)

CS

Content Date

(0008,0023)

Content Time

(0008,0033)

Lily MedTech Inc.

ALWAYSAUTO

ALWAYSAUTO

DA

ALWAYS

AUTO

TM

ALWAYS

AUTO

“L\F”

34 / 38

LS00-M00005 Rev.00

COCOLY DICOM Conformance Statement
Table 5.1-10
IMAGE PLANE MODULE OF CREATED SOP INSTANCES
Attribute Name

Tag

VR

Value

Presence

Sourceof Value
Pixel Spacing(0028,0030)

DS

ALWAYS

AUTO

Image Orientation(0020,0037)

DS

ALWAYS

AUTO(0020,0032)

DS

ALWAYS

AUTO

Slice Thickness(0018,0050)

DS

ALWAYS

AUTO

Slice Location(0020,1041)

DS

ALWAYS

AUTO“1\0\0\0\0\-1”(Patient)
Image Position(Patient)

Table 5.1-11
IMAGE PIXEL MODULE OF CREATED SOP INSTANCES
Attribute Name

Tag

VR

Value

Presence

Sourceof Value
Pixel Data

(7FE0,0010)

OW

Image data

ALWAYS

AUTO

Samples per Pixel(0028,0002)

US

“1”

ALWAYS

AUTO

Photometric(0028,0004)

CS“MONOCHROME2”ALWAYS

AUTO

Rows(0028,0010)

US

512

ALWAYS

AUTO

Columns(0028,0011)

US

512

ALWAYS

AUTO

Bits Allocated(0028,0100)

US

See section 5.1.1.4

ALWAYS

AUTO

Bits Stored(0028,0101)

US

for CT Image IOD.

ALWAYS

AUTO

High Bit(0028,0102)

US

See section 5.1.1.5

ALWAYSAUTO

ALWAYSAUTO

ALWAYS

AUTO

Interpretation

for US Image IOD.
Pixel Representation(0028,0103)

US“1”
for CT Image IOD“0”
for US Image IOD.

Pixel Aspect Ratio

Lily MedTech Inc.

(0028,0034)

IS

“1\1”

35 / 38

LS00-M00005 Rev.00

COCOLY DICOM Conformance Statement
Table 5.1-12
SOP COMMON MODULE OF CREATED SOP INSTANCES
Attribute NameSOP Class UID

Tag

VR

Value

(0008,0016)

UI“1.2.840.10008.5.1

Presenceof ValueSourceALWAYSAUTO

ALWAYSAUTO

ALWAYS

AUTO.4.1.1.2”
for CT Image IOD“1.2.840.10008.5.1.4.1.1.6.1”
for US Image IOD
SOP Instance UID(0008,0018)

UI

Specific Character Set(0008,0005)

CS“\ISO 2022 IR 87”

Table 5.1-13
ADDITIONAL ATTRIBUTE OF CREATED SOP INSTANCES
Attribute Name
Spacing Between

Tag

VR

(0018,0088)

DS

Value

Presenceof Value
ANAP

SourceUSER

SlicesLily MedTech Inc.

36 / 38

LS00-M00005 Rev.00

COCOLY DICOM Conformance Statement
CT Image Module
Table 5.1-14
CT IMAGE MODULE OF CREATED SOP INSTANCES
Attribute Name

Tag

VR

Value

Presence

Sourceof Value
Image Type

(0008,0008)

CS“ORIGINAL\PRIMAR

ANAP

AUTO

Y”
Samples per Pixel(0028,0002)

US

“1”

ALWAYS

AUTO

Photometric(0028,0004)

CS“MONOCHROME2”ALWAYS

AUTO

Bits Allocated(0028,0100)

US

“16”

ALWAYS

AUTO

Bits Stored(0028,0101)

US

“12”

ALWAYS

AUTO

High Bit(0028,0102)

US

“11”

ALWAYS

AUTO

Rescale Intercept(0028,1052)

DS

“0”

ALWAYS

AUTO

Rescale Slope(0028,1053)

DS

“1”

ALWAYS

AUTO

KVP(0018,0060)

DS

EMPTY

AUTO

Acquisition Number(0020,0012)

IS

EMPTY

AUTO

Interpretation

US Image Module
Table 5.1-15
IOD OF CREATE Ultrasound Image SOP INSTANCE
Attribute Name

Tag

VR

Value

Presence

Sourceof Value
Image Type

(0008,0008)

CS“ORIGINAL\PRIMAR

ANAP

AUTO

Y”
Samples per Pixel(0028,0002)

US

“1”

ALWAYS

AUTO

Photometric(0028,0004)

CS“MONOCHROME2”ALWAYS

AUTO

Bits Allocated(0028,0100)

US

“8”

ALWAYS

AUTO

Bits Stored(0028,0101)

US

“8”

ALWAYS

AUTO

High Bit(0028,0102)

US

“7”

ALWAYS

AUTO

Pixel Representation(0028,0103)

US

“0”

ALWAYS

AUTO

Interpretation

Lily MedTech Inc.

37 / 38COCOLY DICOM Conformance Statement

LS00-M00005 Rev.00

5.2. DATA DICTIONARY OF PRIVATE ATTRIBUTESNo Data Dictionary of Private attributes are supported.

5.3. CODED TERMINOLOGY AND TEMPLATESNo Coded Terminology and Templates are supported.

5.4. GRAYSCALE IMAGE CONSISTENCYNo Grayscale Image Consistency are supported.

5.5. STANDARD EXTENDED / SPECIALIZED / PRIVATE SOP CLASSESNo Specialized or Private SOP Classes are supported.

5.6. PRIVATE TRANSFER SYNTAXESNo Private Transfer Syntaxes are supported.

Lily MedTech Inc.

38 / 38