Database

The database that ships with the LEAD Medical Storage Server uses over 30 different tables to store all types of data, including configuration, logging, users, passwords, client communication information (application entities), options, presentation states, and so on.  This tutorial focuses on patient, study, series, and instance data (i.e. “medical data”.).

The shipping database uses the following tables to store the medical data:

• Patient
• OtherPatientIDs

• OtherPatientNames

• Study

• OtherStudyNumbers
• ReferencedStudySequence

• ProcedureCodeSequence

• Series

• ReferencedPerformedProcedureStepSequence

• Instance

• ReferencedImageSequence
• ReferencedImages

• PresentationInstance

• ReferencedPatientSequence

• ReferencedSeriesSequence
• RequestAttributeSequence       

For the sample database tutorial, we define a much simpler database schema with four tables:

• MyPatientTable - stores the patient information
• MyStudyTable - stores the study information
• MySeriesTable - stores the series information
• MyInstanceTable - stores the instance information 

It is logical to have a schema that contains at least these four tables, since there is a one-to-many relationship between patient, study, series, and instance data: 

• A patient can have one or more studies. 
• A study can consist of one or more series. 
• A series can contain one or more instances. 

Note that this basic structure is logical, but not required.  If you choose to do so, you could have a single table containing all the information.  

Below is a graphical representation of the sample schema used in this tutorial: 

The shipping database schema uses the following primary keys:

For the tutorial schema, the primary key of each table will be an identity key that is automatically created for each record.   For example, the first patient record that is added to table MyPatientTable will have the primary key PatientId automatically generated, and will have a value of ‘1’.  The next patient record added will have a PatientId of ‘2’ automatically generated.  The same holds for MyStudyTable and the primary key StudyId, MySeriesTable and SeriesId, and MyInstanceTable and ImageId.