Introduction:

The LEAD Medical Storage Server is configured to use a specific database schema for storing patient, study, series, and instance information. However, the LEAD Medical Storage Server can be configured to instead use a database with a different schema to store this information.  This tutorial describes the architecture and necessary steps to achieve this.  In this tutorial, you will be creating a sample SQL database and connecting it to the LEAD Medical Storage Server.

Throughout this tutorial, any class that is defined to allow database interaction with the new schema is prefaced by “My”.  This includes new classes and classes that override existing classes.

Internally, the LEAD Medical Storage Server uses the System.Data.DataSet class to act as the interface between the application and the database.  Any data that is read from the database is read into a System.Data.DataSet.  Likewise, any data that is written to the database is first stored in a System.Data.DataSet object, and then written to the database. 

The tutorial is divided into topics.  The first few topics describe how existing components work in the default implementation, how the default behavior needs to be modified to work with another database, and finally how the behavior needs to be specifically modified to work with the tutorial sample database.  The last topc is the actual tutorial – it lists only the specific steps to connect the storage server to the tutorial database.

Topics:

• Data Access Layer
• Database
• Table Relationships
• Storage Catalog
• Database Queries
• Custom Medical Storage Data Access Layer
• Strongly Typed DataSet Class and XML Schema
• Registering the Medical Storage Data Access Layer
• Specifying C-FIND-Rsp DICOM Elements
• My.Medical.Storage.Configuration Addin
• Database Mapping for the Database Manager
• Forwarding (Optional)
• Tutorial: Sample database for the LEAD Storage Server
• Restoring the LEAD Storage Server