[This is preliminary documentation and is subject to change.]
Namespaces| Namespace | Description |
|---|---|
| Dvtk | The main component interface for the Dicom Validation ToolKit. This assembly can be used to perform DICOM validation tests. The Sessions namespace defines various session classes. Validation tests are performed within the context of sessions. The Events namespace defines events to signal the user (integrating application) about reports generated by the component. The Setup is an entry-point for the component. It is used to ensure that the component is properly initialized and terminated. The Security namespace is used to set certificates and credentials used within a test session. The Certificates namespace is used to create test certificates. |
| Dvtk.Certificates |
Contains a certificate generator. Use this generator to create new certificate files.
|
| Dvtk.CommonDataFormat | |
| Dvtk.Comparator | |
| Dvtk.Comparator.Bases | |
| Dvtk.Comparator.Convertors | |
| Dvtk.Dicom.InformationEntity | |
| Dvtk.Dicom.InformationEntity.DefaultValues | |
| Dvtk.Dicom.InformationEntity.QueryRetrieve | |
| Dvtk.Dicom.InformationEntity.Worklist | |
| Dvtk.DvtkDicomEmulators.Bases | |
| Dvtk.DvtkDicomEmulators.MppsClientServers | |
| Dvtk.DvtkDicomEmulators.MppsMessageHandlers | |
| Dvtk.DvtkDicomEmulators.PrintClientServers | |
| Dvtk.DvtkDicomEmulators.PrintMessageHandlers | |
| Dvtk.DvtkDicomEmulators.QueryRetrieveClientServers | |
| Dvtk.DvtkDicomEmulators.QueryRetrieveMessageHandlers | |
| Dvtk.DvtkDicomEmulators.StorageClientServers | |
| Dvtk.DvtkDicomEmulators.StorageCommitClientServers | |
| Dvtk.DvtkDicomEmulators.StorageCommitMessageHandlers | |
| Dvtk.DvtkDicomEmulators.StorageMessageHandlers | |
| Dvtk.DvtkDicomEmulators.WorklistClientServers | |
| Dvtk.DvtkDicomEmulators.WorklistMessageHandlers | |
| Dvtk.Events | Events may be used to tightly couple a GUI application to the component. The events provide a continues progress about activities performed by the component during the validation process. These activities have various levels. The listening application can subscribe to these events by means of a ActivityReportEventHandler. |
| Dvtk.Hl7 | |
| Dvtk.Hl7.Messages | |
| Dvtk.IheActors.Actors | |
| Dvtk.IheActors.Bases | |
| Dvtk.IheActors.Dicom | |
| Dvtk.IheActors.Hl7 | |
| Dvtk.IheActors.Hl7.WebService | |
| Dvtk.IheActors.Hl7.WebService.Generation | |
| Dvtk.IheActors.Hl7.WebService.Validation | |
| Dvtk.IheActors.IheFramework | |
| Dvtk.IheActors.IntegrationProfile | |
| Dvtk.IheActors.UserInterfaces | |
| Dvtk.Results | |
| Dvtk.Security |
During communication over TCP/IP, the OpenSSL protocols may be used.
This requires the use of certificates (public keys) and credentials (private keys).
The classes within this namespace are used to set the certificates and credentials
for the validation test session.
|
| Dvtk.Sessions | Validation tests are performed within the context of sessions. There are three kinds of sessions supported by the component; There is a large collection of interfaces defined within this namespace. DO NOT BE INTIMIDATED by the number of interfaces. They just provide views on top of the session classes. A session class typically implements several interfaces. |
| DvtkApplicationLayer | |
| DvtkApplicationLayer.UserInterfaces | |
| DvtkData |
The classes within the DvtkData namespace are the data-classes that represent
dicom messages and dul messages as well as validation data generated by the Dicom Validation Tool.
|
| DvtkData.Activities |
Activities are used internally by the DVTK component to
report validation activities to the connection application layer.
These classes should not be directly used by the end-user. |
| DvtkData.Collections |
In many cases we might like to extend the collection classes provided by the framework.
Maybe we need to ensure that only objects of certain types are stored in the collection
or we need a different sorting algorithm.
Either way, custom collection classes will de-/serialize properly as long as they
implement IEnumerable or ICollection and, of course, we supply enough information
about the types stored inside the collection. Keep in mind that only the items that
can be accessed through the interfaces are serialized,
public properties and fields are not, unless they return a class
that itself implements ICollection.
There is another caveat when you implement your own container classes:
The implementation of the XmlSerializer requires the collection to have
a default accessor, even though ICollection does not require it.
In VB.Net a default accessor is implemented as an Item property with a single
parameter of type Integer. In C# it is implemented as an indexer.
The syntax for an indexer resembles a read-only property, but it uses
the square brackets around the parameter.
These collection classes are internally used by the component. In .Net 2.x (Whidbey) the System.Collections namespace will support templated strong-typed collections. We may improve this part of the component to use that mechanism. |
| DvtkData.ComparisonResults | |
| DvtkData.Dimse |
This namespace contains data classes related to the DICOM communication-layer;
DIMSE (Dicom Messaging Service Element).
|
| DvtkData.Dul |
This namespace contains data classes related to the DICOM communication-layer;
DUL (Dicom Upper Layer).
|
| DvtkData.DvtDetailToXml | |
| DvtkData.Media |
This namespace contains data classes that represent DICOM media files and their
contents.
|
| DvtkData.Results |
This namespace contains data classes used to represent the results of the
Dicom Validation Tool validation process.
These classes are the output of the Dicom Validation Toolkit. Many of these classes are public. However these classes are only public to allow serialization into an XML output document. These classes should not be used directly by the end-user. The classes should not be instantiated by the end-user. |
| DvtkData.Validation |
This namespace contains data classes used to represent the results of the
Dicom Validation Tool validation process.
These classes are the output of the Dicom Validation Toolkit. Many of these classes are public. However these classes are only public to allow serialization into an XML output document. These classes should not be used directly by the end-user. The classes should not be instantiated by the end-user. |
| DvtkData.Validation.SubItems | |
| DvtkData.Validation.TypeSafeCollections | |
| DvtkHighLevelInterface.Common.Compare | |
| DvtkHighLevelInterface.Common.Messages | |
| DvtkHighLevelInterface.Common.Other | |
| DvtkHighLevelInterface.Common.Threads | |
| DvtkHighLevelInterface.Common.UserInterfaces | |
| DvtkHighLevelInterface.Comparator | |
| DvtkHighLevelInterface.Dicom.Files | |
| DvtkHighLevelInterface.Dicom.Messages | |
| DvtkHighLevelInterface.Dicom.Other | |
| DvtkHighLevelInterface.Dicom.Threads | |
| DvtkHighLevelInterface.Dicom.UserInterfaces | |
| DvtkHighLevelInterface.Hl7.Messages | |
| DvtkHighLevelInterface.Hl7.Threads | |
| DvtkHighLevelInterface.InformationModel |