Rogan Dicom Modality Worklist Server - DelftDI

Document Number: 196.854 00Rogan DicomModality WorklistServerDICOMConformanceStatementRogan-Delft B.V.Page 1 of 1Version: 1.1

Document Number: 196.854 00How to contact:Rogan-Delft BVWiltonstraat 413905 KW VeenendaalThe NetherlandsTel: 31 318 583450Fax: 31 318 583470Email: info@rogan-delft.comWebsite: ww w.rogan-delft.com 2000-2004 Rogan-Delft B.V., Veenendaal (NL). All rights reserved.HyperPACS is a registered trademark of Rogan-Delft B.V. Microsoft, MS-DOS and Windows areregistered trademarks of Microsoft Corporation.Information in this manual is subject to change without notice.Document Name:Document Number:DICOM Modality Worklist Server Conformancestatement196.854CopyrightAll rights reserved. No part of this manual may be reproduced or transmitted in any formwhatsoever, including photocopying and recording without written permission of thecopyright holder: Rogan-Delft B.V., Wiltonstraat 41, 3905 KW VEENENDAAL, TheNetherlands.Concerning this publicationInformation contained in this publication is subject to change without notice.Neither Rogan-Delft B.V. and its subsidiaries nor anyone else who has been involvedwith the development, production or delivery of the documentation be liable for anyspecial, incidental or consequential damages, whether based upon breach of warranty,breach of contract, negligence, strict liability in tort or any other legal theory.Rogan-Delft B.V.Page 2 of 2Version: 1.1

Document Number: 196.854 00Table Of Contents1INTRODUCTION .42IMPLEMENTATION MODEL .52.12.22.33APPLICATION DATA FLOW DIAGRAM .5FUNCTIONAL DEFINITION OF AE.5SEQUENCING OF REAL- WORLD ACTIVITIES .5AE SPECIFICATIONS.63.1ROGAN DICOM MODALITY W ORKLIST SERVER SPECIFICATION .63.1.1ASSOCIATION ESTABLISHMENT POLICIES .63.1.1.13.1.1.23.1.1.33.1.1.43.1.23.1.3General. 6Number of Associations. 6Asynchronous Nature. 6Implementation Identifying Information . 6ASSOCIATION INITIATION POLICY .6ASSOCIATION ACCEPTANCE POLICY.73.1.3.1Echo Request . 73.1.3.1.1 Real-world Activity Associated with Echo Request. 73.1.3.1.2 Accepted Presentation Context . 73.1.3.1.2.1 SOP specific Conformance to the supported Verification SOP Class . 73.1.3.1.3 Presentation context acceptance criterion. 73.1.3.1.4 Transfer syntax selection policies . 73.1.3.2Find Request . 83.1.3.2.1 Real-world Activity Associated with Find Request. 83.1.3.2.2 Accepted Presentation Contexts. 83.1.3.2.2.1 SOP Specific Conformance to the Supported Find SOP Classes. 83.1.3.2.3 Presentation Context Acceptance Criterion. 93.1.3.2.4 Transfer Syntax Selection Policies . 94COMMUNICATION PROFILES .104.1SUPPORTED COMMUNICATIONS STACKS .104.2TCP/IP STACK .104.2.1Physical Media Support.105EXTENSIONS / SPECIALIZATIONS / PRIVATIZATIONS.106CONFIGURATION .106.16.27AE TITLE/PRESENTATION ADDRESS MAPPING .10CONFIGURABLE PARAMETERS .10SUPPORT OF EXTENDED CHARACTER SETS .10Rogan-Delft B.V.Page 3 of 3Version: 1.1

Document Number: 196.854 001IntroductionRogan DICOM Modality WorklistServer is a DICOM Modality Worklist Server that acceptsvisit orders from a HIS or a RIS either through ASCII import, HL7 messages or manualdata entry, and exports this data to Modalities that can act as DICOM Modality WorklistClients.Since it acts as a channel between the HIS/RIS and the Modalities, it is important torealize that the modalities can only receive data that is exported by the informationsystem. If the IS (Information System) does not send a required field to Rogan DICOMModality WorklistServer, the conformance cannot be guaranteed. Contact Rogan for a listof IS's that have been validated.Rogan-Delft B.V.Page 4 of 4Version: 1.1

Document Number: 196.854 002Implementation Model2.1 Application Data Flow DiagramRogan DICOM Modality WorklistServer is located between the HIS/RIS and the Modalitiesin the following manner:The actual input of the HIS/RIS data is provided by a separate product called LINK Pro,but as the availability of certain types of work list data is dependent on LINK Pro and itsinteraction with the IS, some of the configuration descriptions in this document refer toLink Pro.2.2Functional Definition of AEDICOM standardInterface LayerHL7 Interface LayerHL7ORMADTROGAN klistSCUNFS Interface LayerASCII FileRepositoryDataEntryFigure 1: DICOM Standard Interface LayerThe HIS actively sends out order messages to the Rogan DICOM Modality WorklistServer. They are kept there in a local database. When a modality desires to acquireimages, it creates an association with Rogan DICOM Modality Worklist Server and sendsa C-FIND-RQ message with a query. Rogan DICOM Modality Worklist Server performsthe query and replies with a number of C-FIND-RSP messages, to return the matchesfound in the database, if any.2.3 Sequencing of Real-world ActivitiesNot applicable.Rogan-Delft B.V.Page 5 of 5Version: 1.1

Document Number: 196.854 003AE SpecificationsThere is only one Application Entity. Rogan DICOM Modality Worklist Server responds toany AE Title that is sent in an association request, so the AE Title does not have to beconfigured.3.1 Rogan DICOM Modality Worklist Server SpecificationRogan DICOM Modality Worklist Server provides Standard Conformance to the followingDICOM V3.0 SOP Classes:SOP Class name:Verification SOP ClassModality Worklist InformationModel - FINDSOP Class OCIATION ESTABLISHMENT POLICIES3.1.1.1GeneralSCUxxSCPxxRogan DICOM Modality Worklist Server is able to accept requested associations. The PDUsize is unlimited.3.1.1.2Number of AssociationsRogan DICOM Modality Worklist Server can accept any number of concurrentassociations, only limited by physical resources like memory and disk space.3.1.1.3Asynchronous NatureNo asynchronous messages are accepted.3.1.1.4Implementation Identifying InformationThe Implementation Class UID is 1.2.528.1.1008.10000.201.The current Implementation version name is ROGAN DICOM 2013.1.2ASSOCIATION INITIATION POLICYNot applicable.Rogan-Delft B.V.Page 6 of 6Version: 1.1

Document Number: 196.854 003.1.3ASSOCIATION ACCEPTANCE POLICYRogan DICOM Modality WorklistServer will accept an association from any DICOM AE.3.1.3.1Echo Request3.1.3.1.1 Real-world Activity Associated with Echo RequestRogan DICOM Modality WorklistServer receives an Echo request, commonly from an AEthat acts as a modality, where it is generated by a user or automatically to poll theactivity of Rogan DICOM Modality WorklistServer.3.1.3.1.2 Accepted Presentation ContextThe following Presentation Context will be accepted by Rogan DICOM Modality WorklistServer when receiving an Echo request:AbstractSyntaxNameVerificationSOP NameDICOMImplicit VRLittle CPnoneSOP specific Conformance to the supported Verification SOP ClassNot applicable.3.1.3.1.3 Presentation context acceptance criterionNot applicable, since there is only one context.3.1.3.1.4 Transfer syntax selection policiesNot applicable, since there is only one context.Rogan-Delft B.V.Page 7 of 7Version: 1.1

Document Number: 196.854 003.1.3.2Find Request3.1.3.2.1 Real-world Activity Associated with Find RequestRogan DICOM Modality Worklist Server receives a Find request, commonly from an AEthat acts as a modality, where it is generated by a user or automatically, in order toupdate the list of scheduled procedures.3.1.3.2.2 Accepted Presentation ContextsThe following Presentation Context will be accepted by Rogan DICOM Modality WorklistServer when receiving a Find tmodel –VR LittleFINDEndian3.1.3.2.2.1SOP Specific Conformance to the Supported Find SOP ClassesThe supported keys are those listed as required, on the condition that they are indeedprovided by the HIS/RIS.A typical HL7 message that is accepted by Link Pro has the formMSH \& XXXX YYYMMDDHHMMSS ORM O01 YYYMMDDHHMMSS P 2.2 AL NEPID PATIENT ID PATIENT NAME DATE OF BIRTH GENDERORC NW ACCESSION NUMBEROBR ACCESSION NUMBER PROCEDURE TYPE REASON FORPROCEDURE REFERRING PHYSICIAN SEQUENCE NUMBER ROOM PROCEDUREDATE/TIMEThe configuration of Rogan LINK defines which of these fields are written to whichdatabase record. Currently, the default fields are:PATIENT NAMEPATIENT IDDATE OF BIRTHGENDERACCESSION NUMBERPROCEDURE TYPEREASON FOR PROCEDUREREFERRING PHYSICIANSEQUENCE NUMBERROOMPROCEDURE DATEPROCEDURE TIMERogan-Delft B.V.Page 8 of 8Version: 1.1

Document Number: 196.854 00Up to 10 fields can be added to the Link Pro database to add extra fields.When a Rogan DICOM Modality WorklistServer query is received, these database recordsare converted to Scheduled Procedures. Each field has a default mapping:PATIENT NAMEPATIENT IDDATE OF BIRTHGENDERACCESSION NUMBERPROCEDURE TYPEREASON FOR PROCEDUREREFERRING PHYSICIANSEQUENCE NUMBERROOMPROCEDURE DATEPROCEDURE 0020040,0003On installation, the mapping can be redefined. For each DICOM group-element pair onecan specify the database field from which it is filled. The same database field can beplaced in multiple DICOM fields, to accommodate groups of different modalities that allexpect the comments in different places, or, for example, the users wish the proceduretype to be sent as the study description as well.A translation table can be defined for each field. This allows for example the ROOM codeto be converted to the DICOM Modality that is found in the corresponding physical room,and to the AE Title for that modality.For each field, a default value can be defined. Even if the field is not in the database, thisvalue can be added to each procedure.In short, this allows the institution to export all HIS/RIS supplied data in a form that isacceptable for the modalities. If the HIS/RIS does not supply data that is required by themodality, there is an interoperability problem that cannot be solved by the type ofmiddleware that Rogan DICOM Modality Worklist Server represents.The current IS's for which Rogan DICOM Modality Worklist Server has been validatedalways contain one Procedure Step per Procedure.3.1.3.2.3 Presentation Context Acceptance CriterionNot applicable, since there is only one context.3.1.3.2.4 Transfer Syntax Selection PoliciesNot applicable.Rogan-Delft B.V.Page 9 of 9Version: 1.1

Document Number: 196.854 004Communication Profiles4.1 Supported Communications StacksRogan DICOM Modality Worklist Server provides DICOM V3.0 TCP/IP NetworkCommunication Support as defined in PS 3.84.2 TCP/IP StackRogan DICOM Modality Worklist Server uses the WinSock TCP/IP stack as provided bythe Windows NT/2000 operating system.4.2.1Physical Media SupportHYPERWorklistServer can connect to any medium that supports TCP/IP or the PC-AT bus.5Extensions / Specializations /PrivatizationsNone.6Configuration6.1 AE Title/Presentation Address MappingNot applicable.6.2 Configurable ParametersMost properties of Rogan DICOM Modality Worklist Server can be configured through theWindows registry.The following are relevant for its DICOM properties. TCP/IP Port Extended character set Mapping of HIS/RIS data to DICOM fields7Support of Extended Character SetsRogan DICOM Modality Worklist Server supports a single extended character set to bedefined. The default is ISO IR 100.It is assumed that this is the character set in which the IS delivers its data.Rogan DICOM Modality Worklist Server is a registered trademark of Rogan-Delft BV.Specifications are subject to change without any notice.Rogan-Delft B.V.Page 10 of 10Version: 1.1

Rogan DICOM Modality WorklistServer is a DICOM Modality Worklist Server that accepts visit orders from a HIS or a RIS either through ASCII import, HL7 messages or manual data entry, and exports this data to Modalities