LEADTOOLS medical storage server custom database tutorial series

LEADTOOLS Recognition Imaging SDK is a selected LEADTOOLS SDK feature set designed to build end-to-end document imaging applications in enterprise-level document automation solutions. These solutions require OCR, MICR, OMR, barcode, form recognition and processing, PDF , Print capture, archive, annotation and image viewing functions. This powerful tool utilizes LEAD's award-winning image processing technology to intelligently recognize document functions that can be used to identify and extract any type of scanned or faxed image data.

LEADTOOLS Recognition Imaging SDK trial version

Overview

LEAD Medical Storage Server can be configured to use a specific database model to store patient test data and instance information. At the same time, LEAD Medical Storage Server can also be configured to use databases with different architectures to store this information. It describes the architecture and necessary steps to achieve the above goals. In this tutorial, you will learn to create a sample SQL database and connect it to the LEAD medical storage server.

Introduction to the "Custom Database" series of tutorials

In this series of articles, any class defined to allow the database to interact with the new mode begins with "I". This includes new classes and classes that overwrite existing classes.

Internally, the LEAD medical storage server uses the System.Data.DataSet class as the interface between the application and the database. Any data read from the database is read into System.Data.DataSet. Similarly, any data written to the database is first stored in the System.Data.DataSet object and then written to the database.

This blog is divided into 11 topics. The first few topics described how existing components work in replacement mode, how to modify behaviors to work with other databases, and how to modify specific behaviors to use the tutorial sample database. The following topic is the actual tutorial: it only lists the specific steps to connect the storage server to the tutorial database. The last topic describes how to restore the LEAD medical storage server to use the replacement LEADTOOLS database.

After implementing this tutorial, it is recommended to read other articles in the series to learn how to map the patterns used by the LEADTOOLS data access layer.

Data access layer

Leadtools.Medical.Storage. Data access layer components include classes that allow users to store, query and modify DICOM composite instances.

The storage data access agent of the IStorageDataAccessAgent interface.

public interface IStorageDataAccessAgent

{

DataSet QueryPatients( MatchingParameterCollection matchingEntitiesCollection )
;

DataSet QueryStudies ( MatchingParameterCollection matchingEntitiesCollection )
;

DataSet QuerySeries ( MatchingParameterCollection matchingEntitiesCollection ) ;

DataSet QueryCompositeInstances ( MatchingParameterCollection
matchingEntitiesCollection ) ;

int MaxQueryResults {get; set;}

bool QueryCompositeInstancesAsync ( MatchingParameterCollection
matchingEntitiesCollection, QueryPageInfo queryPageInfo) ;

void CancelQueryCompositeInstancesAsync(QueryCompositeInstancesArgs args);

event
EventHandler\<QueryCompositeInstancesArgs\>QueryCompositeInstancesStarting;

event EventHandler
\<QueryCompositeInstancesArgs\>QueryCompositeInstancesCompleted;

int FindPatientsCount ( MatchingParameterCollection matchingEntitiesCollection )
;

int FindStudiesCount ( MatchingParameterCollection matchingEntitiesCollection )
;

int FindSeriesCount ( MatchingParameterCollection matchingEntitiesCollection ) ;

int FindCompositeInstancesCount ( MatchingParameterCollection
matchingEntitiesCollection ) ;

bool IsPatientsExists ( string patientID ) ;

bool IsStudyExists ( string studyInstanceUID ) ;

bool IsSeriesExists ( string seriesInstanceUID ) ;

bool IsCompositeInstancesExists ( string sopInstanceUID ) ;

void UpdateCompositeInstance ( CompositeInstanceDataSet compositeInstanceDataSet
) ;

void StoreDicom ( DicomDataSet dataSet,

string referencedFileName,

string retrieveAe,

ReferencedImages[] images,

bool updateExistentPatient,

bool updateExistentStudy,

bool updateExistentSeries,

bool updateExistentInstances ) ;

int DeletePatient ( MatchingParameterCollection matchingEntitiesCollection ) ;

int DeleteStudy ( MatchingParameterCollection matchingEntitiesCollection ) ;

int DeleteSeries ( MatchingParameterCollection matchingEntitiesCollection ) ;

int DeleteInstance ( MatchingParameterCollection matchingEntitiesCollection ) ;

}
In the tutorial of connecting the sample database to LEAD server storage, you can create and implement the MyStorageSqlDbDataAccessAgent of the IStorageDataAccessAgent interface. Since this tutorial will use SQL Server 2008 as the database engine, our MyStorageSqlDbDataAccessAgent class will derive directly from the existing StorageSqlDbDataAccessAgent class (it implements IStorageDataAccessAgent), and only prepare methods to cover SQL queries. If you don't want to use a SQL-based database engine, your storage data access agent can directly implement IStorageDataAccessAgent members.
understand more

This is the first article in this series. Here we introduce the basic concepts of the data access layer. We will focus on the introduction in the second article in the "Lead Medical Storage Server Custom Database Series Tutorial-Database" series The basic concept of LEAD medical storage server database.

If you want to purchase LEADTOOLS genuine license, or for more product information, please click [Consult online customer service]

Guess you like

Origin blog.51cto.com/15078157/2588668