DICOM PS3.2 2020a - Conformance |
Page 151 |
Attribute Name |
Tag |
N-Create |
N-Set |
>>Code Value |
(0008,0100) |
Y |
Y |
>>Coding Scheme Designator |
(0008,0102) |
Y |
Y |
>>Code Meaning |
(0008,0104) |
Y |
Y |
>Quantity Sequence |
(0040,0293) |
Y |
Y |
>>Quantity |
(0040,0294) |
Y |
Y |
>>Measuring Units Sequence |
(0040,0295) |
Y |
Y |
>>>Code Value |
(0008,0100) |
Y |
Y |
>>>Coding Scheme Designator |
(0008,0102) |
Y |
Y |
>>>Code Meaning |
(0008,0104) |
Y |
Y |
Database Updates
Updates Supply table if Coding Scheme Designator for Billing Item Sequence is DICOMRIS_SUPPLY and the Code Value is a value from this
Code Set
The list below details the behavior of DICOMSRV on occurrence of certain MPPS events and with respect to the coercion of attributes and duration of storage of MPPS messages:
•Reception of a New MPPS Instance - The MPPS message is stored in the database. DICOMSRV will then extract the Patient ID (0020,0010)andasmanyAccessionNumbers(0008,0050)asthereareitemsintheScheduledStepAttributeSequence(0040,0270) fromtheN-CREATEandtrytomatchthesevaluesagainstthePatientMedicalRecordNumberandoneormoreAccessionNumbers in the DICOMRis database. If a non-matching N-CREATE is received, it and any following N-SETs will be marked as exceptions. These exceptions can be reconciled using the RisView application. Otherwise, DICOMSRV will:
•Update its database with values contained in the N-CREATE per table above.
•Update the state of each referenced procedure if so configured.
•UpdateofMPPSto'DISCONTINUED'or'COMPLETED'-TheN-SETisstoredinthedatabase.IftheprecedingN-CREATEmatched then the following is done:
•The attribute values in the N-SET will be used to update the DICOMRis database per table above.
•Update the state of each referenced procedure if so configured.
•Coercion of Attributes - DICOMSRV will coerce attributes as specified in Table C.8.1-3. This coercion may occur when a given step is set to the 'IN PROGRESS' or 'COMPLETED' or 'DISCONTINUED'
•Storage Duration for MPPS Messages - MPPS messages are purged from the DICOMRis database after a configurable period of time has elapsed since the step has been set to a final state or was last updated.
Table C.4.2-11. MPPS N-CREATE/N-SET Response Status Reasons
Service |
Further Meaning |
Error Code |
Reasons |
Status |
|
|
|
Success |
Successful completion of the |
0000 |
The response status code and meaning are logged in the job log file. |
|
N-SET or N-CREATE Request |
|
|
Failure |
Processing Failure |
0110 |
Internal error within DICOMSRV. The response status code and |
|
|
|
meaning are logged in the job log file. |
|
Duplicate SOP Instance |
0111 |
This status is returned when the SCU has attempted to N-CREATE |
|
|
|
a SOP Instance that has already been created. The response status |
|
|
|
code and meaning are logged in the job log file |
|
No such SOP Instance |
0112 |
Status returned when the SCU is trying to SET a SOP instance that |
|
|
|
has not been created. The response status code and meaning are |
|
|
|
logged in the job log file |
|
Missing Attribute |
0120 |
This status is returned if an attribute required to be sent in the |
|
|
|
N-CREATEorrequiredtobesentbeforecompletionoftheProcedure |
Step has not been sent. The response status code and meaning are logged in the job log file.
- Standard -
Page 152 |
DICOM PS3.2 2020a - Conformance |
C.4.2.1.4.3 Activity - Configured AE Requests Verification
C.4.2.1.4.3.1 Description and Sequencing of Activities
A remote AE sends an Echo Request to verify that DICOMSRV is awake and listening. DICOMSRV responds with success status as long as the request can be parsed.
C.4.2.1.4.3.2 Accepted Presentation Contexts
TableC.4.2-12.AcceptablePresentationContextsforAEDICOMSRVandReal-WorldActivityConfigured
AE Requests Verification
|
|
Presentation Context Table |
|
|
|
Abstract Syntax |
Transfer Syntax |
Role |
Extended |
||
Name |
UID |
Name List |
UID List |
|
Negotiation |
|
|
||||
Verification SOP |
1.2.840.10008.1.1Implicit VR Little Endian |
1.2.840.10008.1.2 |
SCP |
None |
|
Class |
|
Explicit VR Little Endian |
1.2.840.10008.1.2.1 |
|
|
|
|
|
|
||
C.4.2.1.4.3.3 SOP Specific Conformance
DICOMSRV provides Standard conformance to the DICOM Verification service class.
C.4.2.1.4.3.4 Presentation Context Acceptance Criterion
Depending on configuration, DICOMSRV may or may not accept multiple presentation contexts containing the same abstract syntax.
C.4.2.1.4.3.5 Transfer Syntax Selection Policy
Transfer Syntaxes in addition to the default Implicit VR Little Endian may be configured for a given Abstract Syntax using DICOM Tool's configuration files. When this is done, the first Transfer Syntax encountered in the configuration file, which matches a Transfer Syntax offered for a given Presentation Context, will be selected as the accepted Transfer Syntax for that Presentation Context.
C.4.3 Network Interfaces
C.4.3.1 Physical Network Interface
The DICOMRis DICOM applications are indifferent to the physical medium over which TCP/IP executes.
C.4.3.2 Additional Protocols
DHCP support can be configured using the Configuration application. If DHCP is not configured a static IP address is assigned.
If DNS support exists on the local network, then DNS is used for address resolution. The address of the DNS server is retrieved using DHCP if the DHCP option is enabled. If DNS is not supported then the hostnames and addresses are configured in the local hosts file.
C.4.3.3 IPv4 and IPv6 Support
This product supports both IPv4 and IPv6. It does not utilize any of the optional configuration identification or security features of IPv6.
C.4.4 Configuration
C.4.4.1 AE Title/Presentation Address Mapping
The AE Title and port of DICOMSRV is configurable by the user from a GUI-based configuration application. The IP Address is picked by the site and may be changed by a Field Engineer.
- Standard -
|
DICOM PS3.2 2020a - Conformance |
Page 153 |
C.4.4.1.1 Local AE Titles |
|
|
|
Table C.4.2-13. AE Title Configuration Table |
|
Application Entity |
Default AE Title |
Default TCP/IP Port |
DICOMSRV |
Must be configured |
104 |
C.4.4.1.2 Remote AE Title/Presentation Address Mapping
The AE Titles, host names, port numbers and supported Presentation Contexts of remote applications are configured in file DICOM- SRV.cfg. This file is referenced by DICOMTool's software when API calls are made to create Associations to remote AEs
C.4.4.2 Parameters
DICOMSRV configuration parameters related to DICOM communications are below. A blank cell under the 'Default Value' heading indicates that there is no default value for the specific configuration attribute.
Table C.4.2-14. Configuration Parameters Table
Parameter |
Configurable |
General Parameters |
|
Time-out waiting for acceptance or rejection Response to an |
Yes |
Association Open Request |
|
Time-out waiting for response to TCP/IP connect() request. |
Yes |
Time-outforwaitingfordatabetweenTCP/IPpackets.(Low-level |
Yes |
timeout) |
|
Time-out waiting for a response to a DIMSE Request |
Yes |
Time-out waiting for the next DIMSE Request |
Yes |
Debugging Capabilities |
|
Hex Dump DIMSE Messages |
Yes |
Hex Dump Association Messages |
Yes |
TCP/IP Settings |
|
TCP/IP Send Buffer |
Yes |
TCP//IP Receive Buffer |
Yes |
PacketFilter |
Yes |
DICOMSRV Parameters |
|
Maximum Number of Simultaneous Associations |
Yes |
Maximum Number of Associations to a given device |
Yes |
Maximum PDU size the AE can receive |
Yes |
Maximum PDU size the AE can send |
No |
Validation of DICOM Service Messages |
Yes |
Modality Worklist Parameters |
|
Maximum Number of Matches for an MWL Request |
Yes |
Default Value
30 Seconds
15 Seconds
15 Seconds
30 Seconds
60 Seconds
Off
Off
65535 Bytes
65535 Bytes
On. This option enables running of tcpdump utility from the command line to capture TCP packet headers/contents
20
3
65536 Bytes
The lower of the value above and the max PDU size specified by the Remote AE in the Association Request
Validate messages and log validation errors. Do not automatically return error for all validation errors
100
- Standard -
Page 154 |
DICOM PS3.2 2020a - Conformance |
|
|
Parameter |
|
Configurable |
Default Value |
Time period after Scheduled Date/Time to leave SPS entries in |
Yes |
2880 min |
|
the SPS Worklist |
|
|
|
State of Parent Procedure that causes deletion of child SPS |
Yes |
PROCEDURE STARTED |
|
Entries |
|
|
|
Supported Transfer Syntaxes |
|
Yes |
Explicit VR Little Endian |
|
|
|
Implicit VR Little Endian |
Modality Performed Procedure Step Parameters |
|||
Generate charges based on supplies specified in MPPS |
Yes |
Off |
|
transactions |
|
|
|
Purge Period for MPPS transactions in final state |
Yes |
30 days |
|
State to automatically set procedures to for a given AE on receipt |
Yes |
|
|
of matching N-CREATE |
|
|
|
State to automatically set procedures to for a given AE on receipt |
Yes |
|
|
of matching N-SET COMPLETED |
|
|
|
State to automatically set procedures to for a given AE on receipt |
Yes |
|
|
of matching N-SET DISCONTINUED |
|
|
|
Flag specifying support for IHE Trauma cases for a given AE |
Yes |
false |
|
Patient ID Range to be used for Patient Registration for IHE |
Yes |
|
|
Trauma case |
|
|
|
Default Procedure Code to be used for orders for IHE Trauma |
Yes |
|
|
cases |
|
|
|
Supported Transfer Syntaxes |
|
Yes |
Explicit VR Little Endian |
|
|
|
Implicit VR Little Endian |
C.5 Media Interchange
DICOMSRV does not support Media Storage
C.6 Support of Character Sets
DICOMSRV support the following character sets in addition to the default:
•ISO_IR 100
C.7 Security
DICOMSRV does not support any specific security measures
C.8 Annexes
C.8.1 IOD Contents
C.8.1.1 Created SOP Instances
DICOMRis does not create SOP instances
C.8.1.2 Usage of Attributes From Received IODs
Fields from MPPS such as technique and supplies and how they are used.
- Standard -
DICOM PS3.2 2020a - Conformance |
Page 155 |
Table C.8.1-1. Attributes in MPPS IOD Used By DICOMRis Applications
Attribute Name |
Tag |
SOP Common Module |
|
Performed Procedure Step Relationship Module |
|
Scheduled Step Attribute Sequence |
(0040,0270) |
>Accession Number |
(0008,0050) |
Patient ID |
(0010,0020) |
Performed Procedure Step Information |
|
Performed Station AE Title |
(0040,0241) |
Performed Procedure Step Description |
(0040,0254) |
Procedure Code Sequence |
(0008,1032) |
>Code Value |
(0008,0100) |
>Coding Scheme Designator |
(0008,0102) |
>Code Meaning |
(0008,0104) |
Image Acquisition Results |
|
Performed Protocol Code Sequence |
(0040,0260) |
>Code Value |
(0008,0100) |
>Coding Scheme Designator |
(0008,0102) |
>Code Meaning |
(0008,0104) |
Performed Series Sequence |
(0040,0340) |
>Protocol Name |
(0018,1030) |
>Operator's Name |
(0008,1070) |
>Retrieve AE Title |
(0008,0054) |
Billing and Material Management Code |
|
Billing Procedure Step Sequence |
|
>Code Value |
(0008,0100) |
>Coding Scheme Designator |
(0008,0102) |
>Code Meaning |
(0008,0104) |
Film Consumption Sequence |
(0040,0321) |
> Number of Films |
(2100,0170) |
> Medium Type |
(2000,0030) |
> Film Size ID |
(2010,0050) |
Billing Supplies and Devices Sequence |
(0040,0384) |
>Billing Item Sequence |
(0040,0296) |
>>Code Value |
(0008,0100) |
Database Updates
Theseattributesneedtomatchvalues in the DICOMRis database so other data contained in MPPS messages e.g., Dose and Materials data, can updatethedatabaseandbedisplayed by the RisView application as described below
This attribute is used by the MppsSrv application as a key into the DICOM Configuration database to determine if the procedure referenced by the MPPS message should automatically have its state changed
Values for these attributes are accessible using the RisView application if they have been stored
Valuesfortheseattributesarerequired if the RisView application is to display the protocol used to perform the procedure
Can be displayed by RisView application
Valuesareneededfortheseattributes so that the RisView application can display actual supplies and film used to perform a given procedure rather thandefaultvaluesassociatedwiththe given procedure in the DICOMRis database
Thevaluesoftheseattributesmayalso be used to generate charges if the site is configured for charging based on
MPPS
- Standard -