UAT and Release Document

 

UKCTOCS Ultrasound Record Archive System

 

 

 

 

 

 

 

 

 

 

Gynea. Cancer Res. Centre

Institute of Women's Health, UCL

Maple House, 1st floor

149 Tottenham Court Road

London, W1T 7DN

 

Phone: 020 7380 6909

Fax: 020 7380 6929

 

 

 

Document Control

 

Owner

Dr. Andy Ryan (a.ryan@ucl.ac.uk)

Prepared by

Will Stott (will.stott@iee.org)

Filename

UAT-UKCTOCS-URA.doc

Location

UKCTOCS\docs

Date Completed

13-06-2007

Version / Rev No.

V1.6 revision 8

Comments

V1.0 revision 45: Initial draft document  for discussion

V1.1 revision 21: Second draft, corrections to 4.1.1, 4.2,4.3,4.4,4.5, App-D

V1.3 revision 15:  Updated for v1.0.0.17

V1.4 revision 2: Added table for British Date Format

V1.5 revision 14: Added table for File Import Examination

V1.6 revision 7: Updated for release v1.1.0.8

 

Total Words 3706


Contents

                                                                                                                        page

  1. Overview and Sign-off                                                                         3
  2. Deliverables                                                                                         4
  3. Setup for User Acceptance Testing                                                   5
  4. UAT Automated Tests                                                                         6
  5. UAT Manual Tests

                                                                                                                          

 

Appendices

A.  Test Data Description

B.  FIT Result Summary

 

                                                                                                                          

 


1.          Overview and Sign-off

This document defines the criterion for the acceptance of the UKCTOCS Ultrasound Record Archive System.

 

 

1.1       Sign-off

UKCTOCS Ultrasound Record Archive System v1.1.0.8 has been successfully delivered and as described by this document. It is judged suitable for use to archive ultrasound records from the volunteers in the UK Collaborative Trial of Ovarian Cancer Screening.

Signed

 

Dr. A. Ryan                Date

 


2.          Deliverables

The following materials were delivered to Dr. Andy Ryan:

·        CD Containing:

                                                                     i.      Licence

                                                                   ii.      Release Notes

                                                                  iii.      Help System

                                                                 iv.      Installation program for URA System v1.1.0.8

                                                                   v.      Files containing printed material

                                                                 vi.      Source files

·        Printed Material:

                                                                     i.      Licence

                                                                   ii.      Release Notes

                                                                  iii.      UAT and Release Document (this document)

 


3.          Setup for User Acceptance Testing

The System Test Environment is described in the Help System (see Reference, Installation Manual, UAT Environment). You should install the URA System into this environment by running the Installation Program as explained by the ‘UAT Installation’ section of the Help System. Once these steps have been completed you should create the files listed in the PathFilename column of Table 3.2 according the specifications detailed in Appendix A

Note: After running the Installation Program you need to run a number of scripts to setup the databases required for the UAT. This can be done from the ‘Database Admin’ dialog box of osImageManagerApp as described by the Help System.

 

fit.ActionFixture

 

start

osImageManagerLibFIT.DatabaseAdminDialog

 

press

CreateUATFiles

 

Table 3.1: Setup of File for UAT

osImageManagerLibFIT.DatabaseAdminDialogResults

PathFilename

Y2004M02\D04\E0000001\Test001.dicom

Y2004M02\D04\E0000001\Test002

Y2004M02\D04\E0000001\Test003.dicom

Y2004M02\D04\E0000001\Test004

Y2004M02\D04\E0000001\Test005.dicom

Y2004M02\D04\E0000001\Test006

Y2004M02\D04\E0000001\Test007.dicom

Y2004M02\D04\E0000001\Test008

Y2004M02\D04\E0000001\Test009.dicom

Y2004M02\D04\E0000001\Test010.dicom

Y2004M02\D05\E0000001\Test011.dicom

Y2004M02\D05\E0000001\Test012.dicom

Y2004M02\D05\E0000001\Test013.dicom

Y2004M02\D05\E0000001\Test014.dicom

Y2004M02\D05\E0000001\Test015.dicom

Y2004M02\D05\E0000001\Test016.dicom

Y2004M02\D05\E0000001\Test017.dicom

Y2004M02\D05\E0000001\Test018.dicom

Y2004M02\D05\E0000001\Test019.dicom

Y2004M02\D05\E0000001\Test020.dicom

Y2004M02\D05\E0000001\Test021.dicom

Y2004M02\D05\E0000001\Test022.dicom

Y2004M02\D05\E0000002\Test024.dicom

Y2004M02\D04\E0000001\Test023.dico

Table 3.2: Setup of Files for UAT

 

 

You must also remove any existing records from the osImage database by opening the ‘Database Admin’ dialog box and running the script ‘UATCleanImageTable’. You should confirm this has been successful by running the script ‘ListImages’ as shown in Table 3.3

 

fit.ActionFixture

 

start

osImageManagerLibFIT.DatabaseAdminDialogRunScript

 

press

CleanImageTable

 

check

TestImageDb

0

Table 3.3: Setup of Databases for UAT

 


4.          UAT Functional Tests

The system is divided into the following functional areas:

·        Dicom File Header Validation Rules

·        Importing Dicom Files – Story 1,8

·        Correcting Information in Dicom File Header – Story 2

·        URA Database Queries – Story 5

·        Exporting Dicom Files – Story 4

·        UKCTOCS Database Queries – Story 7

Each of the above areas has a set of functional tests which form the criterion for acceptance of the system. Except when specified otherwise the tests should be performed by URATestOperator from the Apollo workstation as described in the Installation Manual

 

 


4.1             Dicom File Header Validation Rules

The Dicom file header contains a number of fields which are read by the system and used to validate whether the file data can be imported directly in the URA database (see s4.2) or whether it requires manual correction (see s4.3). In order for a file header to be considered valid the following conditions must be satisfied:

§         PatientName (0010,0010) corresponds to a record in the Volunteer table; see s4.1.1

§         PatientID (0010,0020) and Study Date (0008.0020) correspond to a record in the UltrscanResults table; see s4.1.2

§         SOP Instance UID (0008,0018) does NOT correspond to a record already in the URA database; see s4.1.3

If the file is deemed invalid it will be added to the list of files requiring manual correction; see User Manual – Importing files.

Note: During the Setup for UAT (Section 3) the Artemis UKCTOCS[1] database and URA database are populated with the records list in Appendix D. The validation in the following tables is performed against these records.


4.1.1       Patient Name (0010,0010)

The following rules are applied:

§         PatientName (from Dicom file) contains a number of elements separated by a caret (^). However, the Dicom specified order is not respected and only the first name and surname are provided.

§         The correct V_VolunteerRef is returned if any element of PatientName matches V_Surname and the first letter of any other element matches the first letter of V_FirstNames in the Volunteers database table. Matches are not case sensitive

§         If the PatientName does not correspond to a record in the Volunteers database table then -1 is returned. This indicates the data in the file header does NOT correspond to a record in the Volunteer table; it is invalid.

Examples of these rules are provided in the following table where the PatientName column represents data found in the Dicom Header and the VolunteerRef column contains the corresponding entry in the Volunteers database table, V_VolunteerRef. The IsValid() column reflects whether the match is  expected to be valid or not.

osImageManagerLibFIT.PatientNameValidation

 

PatientName

VolunteerRef

IsValid()

Will^Stott

99000002

true

Mickie^Mouse

99000002

false

Will^Stott

-1

false

Mickie^Mouse

-1

false

Will^Stott

99000002ABC

false

Will.Stott

99000002

true

Will. Stott

99000002

true

.Will.Stott

99000002

true

.Will .Stott

99000002

true

. Will. Stott

99000002

true

Charles^Petzold

98011111

true

Charles^Petzold

9811111

true

Charles^Petzold

98011111U

true

Charles^Petzold

98011111UUUUU

true

 


4.1.2       Patient ID (0010,0020) and Study Date (0008,0020)

The following rules are applied:

§         The PatientID value is read from the dicom file header and processed as follows:

o       any trailing ‘U’ characters[2] are removed from the string found in the header

o       If the string found in the header is seven characters[3] long then a zero is inserted at index position 2.

§         The StudyDate value read from the dicom file header and processed as follows:

o       Year is obtained from the characters at index 0 to 3

o       Month is obtained from the characters at index 4 to 5

o       Day is obtained from characters at index 6 to 7

o       Year, month and day values are converted into a US_ScanDate data type with the time being set as midnight (00:00:00).

§         If the PatientID value and date obtained from converting StudyDate do NOT correspond to values for US_VolunteerRef and US_Scandate for the same record in the UltrscanResults table then the data is invalid

Note: Although the time element of the US_Scandate field is generally set to 00:00:00 the comparison operation will still  produce a valid match to StudyDate if the time value lies in the range 00:00:00 to 23:59.59

Examples of these rules are provided in the following table where the PatientID and StudyDate columns represents data found in the Dicom Header and the IsValid() column states whether a corresponding entry is expected to be found in the UltrascanResults table; see Appendix D for values.

 

 

osImageManagerLibFIT.PatientIDStudyDateValidation

 

PatientID

StudyDate

IsValid()

99000002

20050121

true

99000002

20060606

false


4.1.3       SOP Instance UID (0008,0018)

The following rule is applied:

§         If the value in the SOPInstanceUID field of the Dicom header matches the DicomRef field of any record in Image table of the URA database then the file is invalid because it has already been imported into the database.

Examples of this rules are provided in the following table where the SOPInstanceUID column represents data found in the Dicom Header and the column labelled and ImageAlreadyExists() contains ‘true’ or ‘false’ depending upon whether there is a corresponding entry in the URA database Image table; see Appendix D for values.

fit.ActionFixture

 

start

osImageManagerLibFIT.FileImportDialogFile

 

enter

ReadFileFromDataDirectory

Test999

check

ImageListCount

1

check

CorrectionListCount

0

check

Progress

1 files read

press

Import

 

check

Progress

1 files imported

 

osImageManagerLibFIT.SOPInstanceUIDValidation

 

SOPInstanceUID

ImageAlreadyExists()

1.2.826.999999.1.9900.1.20050531130000999.1.1.0

true

999

false

 

 

 


4.2             Importing Dicom Files – Story 1, 8

Dicom files are selected using the ImportFile dialog box and then validated using the rules tested in s4.1. Valid files are put in the list ‘images ready to import’ (image list) and invalidate file put in the list ‘images needed attention’ (correction list). The following tests are concerned with importing these valid files and then confirming that the associated records have been created in the URA database.

Note: The tests confirm the functionality required of story 1: “Copy Dicom files from disk and store in database” by listing the actions a user would take to perform this task and then listing the resulting records.

Import the Dicom files from the UAT Data directory using the ImportImage dialog box; see Appendix D

osImageManagerLibFIT.DicomFileList

PathFilename

Y2004M02\D04\E0000001\Test001.dicom

Y2004M02\D04\E0000001\Test002

Y2004M02\D04\E0000001\Test003.dicom

Y2004M02\D04\E0000001\Test004

Y2004M02\D04\E0000001\Test005.dicom

Y2004M02\D04\E0000001\Test006

Y2004M02\D04\E0000001\Test007.dicom

Y2004M02\D04\E0000001\Test008

Y2004M02\D04\E0000001\Test009.dicom

Y2004M02\D04\E0000001\Test010.dicom

Y2004M02\D05\E0000001\Test011.dicom

Y2004M02\D05\E0000001\Test012.dicom

Y2004M02\D05\E0000001\Test013.dicom

Y2004M02\D05\E0000001\Test014.dicom

Y2004M02\D05\E0000001\Test015.dicom

Y2004M02\D05\E0000001\Test016.dicom

Y2004M02\D05\E0000001\Test017.dicom

Y2004M02\D05\E0000001\Test018.dicom

Y2004M02\D05\E0000001\Test019.dicom

Y2004M02\D05\E0000001\Test020.dicom

Y2004M02\D05\E0000001\Test021.dicom

Y2004M02\D05\E0000001\Test022.dicom

Y2004M02\D05\E0000002\Test024.dicom


Confirm that the image records have been created; see Appendix D

 

osImageManagerLibFIT.ImageList

CaptureDate

StoredDate

DiskRef

VolunteerRef

DicomRef

Flags

2005-01-21

2006-08-21

UAT

99000002

1.2.826.999999.1.9900.1.20050531130000999.1.1.0

[---]

 

osImageManagerLibFIT.ImageExtList

DicomRef

DicomFileSize

MaskFile

1.2.826.999999.1.9900.1.20050531130000999.1.1.0

308604

[UAT]MaskFragments\0000999.1.1.0.ura

 

fit.ActionFixture

 

start

osImageManagerLibFIT.DatabaseAdminDialogRunScript

 

press

CleanImageTable

 

check

TestImageDb

0

Table 3.3: Setup of Databases for UAT

 

fit.ActionFixture

 

start

osImageManagerLibFIT.FileImportDialogFile

 

enter

ReadFileFromDataDirectory

Test000

check

ImageListCount

1

check

CorrectionListCount

0

check

Progress

1 files read

press

Import

 

check

Progress

1 files imported

 

 

 

fit.ActionFixture

 

start

osImageManagerLibFIT.FileImportDialogExam

 

press

ReadAllImageDirectory

 

check

ImageListCount

1

check

CorrectionListCount

2

check

Progress

23 files read

 

 

 

Note: Story 8 required that corrections were made to the collection of files found in the same examination directory

 

fit.ActionFixture

 

start

osImageManagerLibFIT.FileImportDialogTree

 

press

ReadAllImageDirectory

 

check

ImageListCount

14

check

CorrectionListCount

8

check

Progress

23 files read

press

Import

 

check

Progress

14 files imported

 


 

 

osImageManagerLibFIT.ImageList

 

CaptureDate

StoredDate

DiskRef

VolunteerRef

DicomRef

Flags

2005-01-21

2006-08-21

UAT

99000002

1.2.826.999999.1.9900.1.20050531130000000.1.1.0

[---]

2005-01-21

2006-08-21

UAT

99000002

1.2.826.999999.1.9900.1.20050531130000001.1.1.0

[---]

2005-01-21

2006-08-21

UAT

99000002

1.2.826.999999.1.9900.1.20050531130000002.1.1.0

[---]

2005-01-21

2006-08-21

UAT

99000002

1.2.826.999999.1.9900.1.20050531130000003.1.1.0

[---]

2005-01-22

2006-08-21

UAT

99000002

1.2.826.999999.1.9900.1.20050531130000004.1.1.0

[---]

2005-01-22

2006-08-21

UAT

99000002

1.2.826.999999.1.9900.1.20050531130000005.1.1.0

[---]

2005-01-22

2006-08-21

UAT

99000002

1.2.826.999999.1.9900.1.20050531130000006.1.1.0

[---]

2006-07-01

2006-08-21

UAT

99000002

1.2.826.999999.1.9900.1.20050531130000007.1.1.0

[---]

2006-07-01

2006-08-21

UAT

99000002

1.2.826.999999.1.9900.1.20050531130000008.1.1.0

[---]

2005-11-01

2006-08-21

UAT

99000002

1.2.826.999999.1.9900.1.20050531130000009.1.1.0

[---]

2003-02-23

2006-08-21

UAT

98011111

1.2.826.999999.1.9900.1.20050531130000010.1.1.0

[---]

2003-02-23

2006-08-21

UAT

98011111

1.2.826.999999.1.9900.1.20050531130000011.1.1.0

[---]

2006-01-23

2006-08-21

UAT

98011111

1.2.826.999999.1.9900.1.20050531130000012.1.1.0

[---]

2006-01-23

2006-08-21

UAT

98555552

1.2.826.999999.1.9900.1.20050531130000013.1.1.0

[---]

2006-01-23

2006-08-21

UAT

98000003

1.2.826.999999.1.9900.1.20050531130000014.1.1.0

[---]

 

 


4.3             Correcting Information in Dicom File Header – Story 2

Dicom files are selected using the ImportFile dialog box and then validated using the rules tested in s4.1. Valid files are put in the list ‘images ready to import’ and invalidate file put in the list ‘images needed attention’. The following tests are concerned with correcting these invalid files so they can be imported and then confirming that the associated records have been created in the URA database.

Note: The tests confirm the functionality required of story 2: “Allow Correction of Errors in Dicom header” by listing the actions a user would take to perform this task and then listing the resulting records.

Correct the header information using the CorrectHeaderDialog

fit.ActionFixture

 

start

osImageManagerLibFIT.FileImportDialogTree

 

press

ReadAllImageDirectory

 

check

ImageListCount

0

enter

SelectFile

IMAGE\Y2004M02\D05\E0000001\Test015.dicom

enter

CorrectPatientName

W^Stott

enter

CorrectPatientID

-

enter

CorrectAppointment

-

press

Correct

 

check

ImageListCount

1

enter

SelectFile

IMAGE\Y2004M02\D05\E0000001\Test016.dicom

enter

CorrectPatientName

-

enter

CorrectPatientID

99000002

enter

CorrectAppointment

-

press

Correct

 

check

ImageListCount

2

enter

SelectFile

IMAGE\Y2004M02\D05\E0000001\Test017.dicom

enter

CorrectPatientName

-

enter

CorrectPatientID

99000002

enter

CorrectAppointment

-

press

Correct

 

check

ImageListCount

3

enter

SelectFile

IMAGE\Y2004M02\D05\E0000001\Test018.dicom

enter

CorrectPatientName

-

enter

CorrectPatientID

-

enter

CorrectAppointment

2006-07-23

press

Correct

 

check

ImageListCount

4

enter

SelectFile

IMAGE\Y2004M02\D05\E0000001\Test019.dicom

enter

CorrectPatientName

-

enter

CorrectPatientID

-

enter

CorrectAppointment

-

press

CorrectDuplicate

 

check

ImageListCount

5

enter

SelectFile

IMAGE\Y2004M02\D05\E0000001\Test020.dicom

enter

CorrectPatientName

-

enter

CorrectPatientID

99000002

enter

CorrectAppointment

-

press

Correct

 

check

ImageListCount

6

enter

SelectFile

IMAGE\Y2004M02\D05\E0000001\Test021.dicom

enter

CorrectPatientName

-

enter

CorrectPatientID

-

enter

CorrectAppointment

2006-07-23

press

Correct

 

check

ImageListCount

7

enter

SelectFile

IMAGE\Y2004M02\D05\E0000001\Test022.dicom

enter

CorrectPatientName

W^Stott

enter

CorrectPatientID

99000002

enter

CorrectAppointment

2006-07-23

press

Correct

 

check

ImageListCount

8

press

Import

 

check

Progress

8 files imported

Check the records present in the database at the end of the test.

osImageManagerLibFIT.ImageList

 

CaptureDate

StoredDate

DiskRef

VolunteerRef

DicomRef

Flags

2006-07-25

2006-08-21

UAT

99000002

1.2.826.999999.1.9900.1.20050531130000000.1.1.1

[-D-]

2005-01-21

2006-08-21

UAT

99000002

1.2.826.999999.1.9900.1.20050531130000001.1.1.0

[---]

2005-01-21

2006-08-21

UAT

99000002

1.2.826.999999.1.9900.1.20050531130000002.1.1.0

[---]

2005-01-21

2006-08-21

UAT

99000002

1.2.826.999999.1.9900.1.20050531130000003.1.1.0

[---]

2005-01-22

2006-08-21

UAT

99000002

1.2.826.999999.1.9900.1.20050531130000004.1.1.0

[---]

2005-01-22

2006-08-21

UAT

99000002

1.2.826.999999.1.9900.1.20050531130000005.1.1.0

[---]

2005-01-22

2006-08-21

UAT

99000002

1.2.826.999999.1.9900.1.20050531130000006.1.1.0

[---]

2006-07-01

2006-08-21

UAT

99000002

1.2.826.999999.1.9900.1.20050531130000007.1.1.0

[---]

2006-07-01

2006-08-21

UAT

99000002

1.2.826.999999.1.9900.1.20050531130000008.1.1.0

[---]

2005-11-01

2006-08-21

UAT

99000002

1.2.826.999999.1.9900.1.20050531130000009.1.1.0

[---]

2003-02-23

2006-08-21

UAT

98011111

1.2.826.999999.1.9900.1.20050531130000010.1.1.0

[---]

2003-02-23

2006-08-21

UAT

98011111

1.2.826.999999.1.9900.1.20050531130000011.1.1.0

[---]

2006-01-23

2006-08-21

UAT

98011111

1.2.826.999999.1.9900.1.20050531130000012.1.1.0

[---]

2006-01-23

2006-08-21

UAT

98555552

1.2.826.999999.1.9900.1.20050531130000013.1.1.0

[---]

2006-01-23

2006-08-21

UAT

98000003

1.2.826.999999.1.9900.1.20050531130000014.1.1.0

[---]

2006-07-21

2006-08-21

UAT

99000002

1.2.826.999999.1.9900.1.20050531130000015.1.1.0

[---]

2006-07-22

2006-08-21

UAT

99000002

1.2.826.999999.1.9900.1.20050531130000016.1.1.0

[---]

2006-07-23

2006-08-21

UAT

99000002

1.2.826.999999.1.9900.1.20050531130000017.1.1.0

[---]

2006-07-23

2006-08-21

UAT

99000002

1.2.826.999999.1.9900.1.20050531130000018.1.1.0

[---]

2006-07-26

2006-08-21

UAT

99000002

1.2.826.999999.1.9900.1.20050531130000020.1.1.0

[---]

2006-07-23

2006-08-21

UAT

99000002

1.2.826.999999.1.9900.1.20050531130000021.1.1.0

[---]

2006-07-23

2006-08-21

UAT

99000002

1.2.826.999999.1.9900.1.20050531130000022.1.1.0

[---]


4.4             URA Database Queries – Story 5

Images in the URA database can be added to the osImageManagerApp treeview by running a number of standard queries from the View menu. The following tests are concerned with confirming these queries populate the treeview as required - FullPath is the location of the record in the treeview hierarchy with a backslash between each level.

Note: The tests confirm the functionality required of story 5: “List images in the application” by listing the results of various standard queries.

fit.ActionFixture

 

start

osImageManagerLibFIT.SelectItemsForImageTreeDialog

 

enter

SetVolunteerRef

0

press

DisplayRecordsForVolunteer

 

 

osImageManagerLibFIT.ImageTreeViewList

 

Text

NodePath

URA

URA

 

fit.ActionFixture

 

start

osImageManagerLibFIT.SelectItemsForImageTreeDialog

 

enter

SetVolunteerRef

99000002

press

DisplayRecordsForVolunteer

 

 

osImageManagerLibFIT.ImageTreeViewList

 

Text

NodePath

URA

URA

UAT-CentreA

URA\UAT-CentreA

99000002

URA\UAT-CentreA\99000002

2006-07-25

URA\UAT-CentreA\99000002\2006-07-25

0000000.1.1.1

URA\UAT-CentreA\99000002\2006-07-25\0000000.1.1.1

2005-01-21

URA\UAT-CentreA\99000002\2005-01-21

0000001.1.1.0

URA\UAT-CentreA\99000002\2005-01-21\0000001.1.1.0

0000002.1.1.0

URA\UAT-CentreA\99000002\2005-01-21\0000002.1.1.0

0000003.1.1.0

URA\UAT-CentreA\99000002\2005-01-21\0000003.1.1.0

2005-01-22

URA\UAT-CentreA\99000002\2005-01-22

0000004.1.1.0

URA\UAT-CentreA\99000002\2005-01-22\0000004.1.1.0

0000005.1.1.0

URA\UAT-CentreA\99000002\2005-01-22\0000005.1.1.0

0000006.1.1.0

URA\UAT-CentreA\99000002\2005-01-22\0000006.1.1.0

2006-07-01

URA\UAT-CentreA\99000002\2006-07-01

0000007.1.1.0

URA\UAT-CentreA\99000002\2006-07-01\0000007.1.1.0

0000008.1.1.0

URA\UAT-CentreA\99000002\2006-07-01\0000008.1.1.0

2005-11-01

URA\UAT-CentreA\99000002\2005-11-01

0000009.1.1.0

URA\UAT-CentreA\99000002\2005-11-01\0000009.1.1.0

2006-07-21

URA\UAT-CentreA\99000002\2006-07-21

0000015.1.1.0

URA\UAT-CentreA\99000002\2006-07-21\0000015.1.1.0

2006-07-22

URA\UAT-CentreA\99000002\2006-07-22

0000016.1.1.0

URA\UAT-CentreA\99000002\2006-07-22\0000016.1.1.0

2006-07-23

URA\UAT-CentreA\99000002\2006-07-23

0000017.1.1.0

URA\UAT-CentreA\99000002\2006-07-23\0000017.1.1.0

0000018.1.1.0

URA\UAT-CentreA\99000002\2006-07-23\0000018.1.1.0

2006-07-26

URA\UAT-CentreA\99000002\2006-07-26

0000020.1.1.0

URA\UAT-CentreA\99000002\2006-07-26\0000020.1.1.0

0000021.1.1.0

URA\UAT-CentreA\99000002\2006-07-23\0000021.1.1.0

0000022.1.1.0

URA\UAT-CentreA\99000002\2006-07-23\0000022.1.1.0

 

fit.ActionFixture

 

start

osImageManagerLibFIT.SelectItemsForImageTreeDialog

 

enter

SetClearTree

true

enter

SetDiskLabel

x

press

DisplayRecordsForDisk

 

 

osImageManagerLibFIT.ImageTreeViewList

 

Text

NodePath

URA

URA

 

fit.ActionFixture

 

start

osImageManagerLibFIT.SelectItemsForImageTreeDialog

 

enter

SetClearTree

true

enter

SetDiskLabel

UAT

press

DisplayRecordsForDisk

 

 

osImageManagerLibFIT.ImageTreeViewList

 

Text

NodePath

URA

URA

UAT-CentreA

URA\UAT-CentreA

99000002

URA\UAT-CentreA\99000002

2006-07-25

URA\UAT-CentreA\99000002\2006-07-25

0000000.1.1.1

URA\UAT-CentreA\99000002\2006-07-25\0000000.1.1.1

2005-01-21

URA\UAT-CentreA\99000002\2005-01-21

0000001.1.1.0

URA\UAT-CentreA\99000002\2005-01-21\0000001.1.1.0

0000002.1.1.0

URA\UAT-CentreA\99000002\2005-01-21\0000002.1.1.0

0000003.1.1.0

URA\UAT-CentreA\99000002\2005-01-21\0000003.1.1.0

2005-01-22

URA\UAT-CentreA\99000002\2005-01-22

0000004.1.1.0

URA\UAT-CentreA\99000002\2005-01-22\0000004.1.1.0

0000005.1.1.0

URA\UAT-CentreA\99000002\2005-01-22\0000005.1.1.0

0000006.1.1.0

URA\UAT-CentreA\99000002\2005-01-22\0000006.1.1.0

2006-07-01

URA\UAT-CentreA\99000002\2006-07-01

0000007.1.1.0

URA\UAT-CentreA\99000002\2006-07-01\0000007.1.1.0

0000008.1.1.0

URA\UAT-CentreA\99000002\2006-07-01\0000008.1.1.0

2005-11-01

URA\UAT-CentreA\99000002\2005-11-01

0000009.1.1.0

URA\UAT-CentreA\99000002\2005-11-01\0000009.1.1.0

UAT-CentreB

URA\UAT-CentreB

98011111

URA\UAT-CentreB\98011111

2003-02-23

URA\UAT-CentreB\98011111\2003-02-23

0000010.1.1.0

URA\UAT-CentreB\98011111\2003-02-23\0000010.1.1.0

0000011.1.1.0

URA\UAT-CentreB\98011111\2003-02-23\0000011.1.1.0

2006-01-23

URA\UAT-CentreB\98011111\2006-01-23

0000012.1.1.0

URA\UAT-CentreB\98011111\2006-01-23\0000012.1.1.0

98555552

URA\UAT-CentreB\98555552

2006-01-23

URA\UAT-CentreB\98555552\2006-01-23

0000013.1.1.0

URA\UAT-CentreB\98555552\2006-01-23\0000013.1.1.0

2006-07-21

URA\UAT-CentreA\99000002\2006-07-21

98000003

URA\UAT-CentreB\98000003

2006-01-23

URA\UAT-CentreB\98000003\2006-01-23

0000014.1.1.0

URA\UAT-CentreB\98000003\2006-01-23\0000014.1.1.0

0000015.1.1.0

URA\UAT-CentreA\99000002\2006-07-21\0000015.1.1.0

2006-07-22

URA\UAT-CentreA\99000002\2006-07-22

0000016.1.1.0

URA\UAT-CentreA\99000002\2006-07-22\0000016.1.1.0

2006-07-23

URA\UAT-CentreA\99000002\2006-07-23

0000017.1.1.0

URA\UAT-CentreA\99000002\2006-07-23\0000017.1.1.0

0000018.1.1.0

URA\UAT-CentreA\99000002\2006-07-23\0000018.1.1.0

2006-07-26

URA\UAT-CentreA\99000002\2006-07-26

0000020.1.1.0

URA\UAT-CentreA\99000002\2006-07-26\0000020.1.1.0

0000021.1.1.0

URA\UAT-CentreA\99000002\2006-07-23\0000021.1.1.0

0000022.1.1.0

URA\UAT-CentreA\99000002\2006-07-23\0000022.1.1.0

 


4.5             Exporting Dicom Files – Story 4

Images in the URA database are selected using the ExportFile dialog box and then copied as Dicom files to the UATOutput directory as defined in Appendix C. The following tests are concerned with confirming that this operation has been performed correctly.

Note: The tests confirm the functionality required of story 4: “Exporting Images to Dicom Files” by listing the actions a user would take to perform this task and then checking resulting file.

fit.ActionFixture

 

start

osImageManagerLibFIT.SelectItemsForImageTreeDialog

 

enter

SetVolunteerRef

99000002

press

DisplayRecordsForVolunteer

 

 

fit.ActionFixture

 

start

osImageManagerLibFIT.FileExportDialog

 

enter

RestoreMask

true

enter

ExportDirectory

output\

enter

RecordToExport

1.2.826.999999.1.9900.1.20050531130000000.1.1.1

press

Export

 

 

 

 

osImageManagerLibFIT.DirectoryList

 

Filename

Size

CRC

99000002-2006-07-25-0000000.1.1.1.dicom

923006

BBDF01F0

ReadMe.txt

35

16E91512

 

 

fit.ActionFixture

 

start

osImageManagerLibFIT.FileExportDialog

 

enter

RestoreMask

false

enter

ExportDirectory

output\

enter

RecordToExport

*

press

Export

 

 


 

osImageManagerLibFIT.DirectoryList

 

Filename

Size

CRC

99000002-2006-07-25-0000000.1.1.1.dicom

923006

9ADEAD24

99000002-2005-01-21-0000001.1.1.0.dicom

308604

9E88CC98

99000002-2005-01-21-0000002.1.1.0.dicom

308604

AA04E8BB

99000002-2005-01-21-0000003.1.1.0.dicom

308604

0F500965

99000002-2005-01-22-0000004.1.1.0.dicom

923006

7DA8D94C

99000002-2005-01-22-0000005.1.1.0.dicom

308604

5F553E04

99000002-2005-01-22-0000006.1.1.0.dicom

308604

6BD91A27

99000002-2006-07-01-0000007.1.1.0.dicom

308604

71BC25AD

99000002-2006-07-01-0000008.1.1.0.dicom

308604

97009102

99000002-2005-11-01-0000009.1.1.0.dicom

308604

203B2923

99000002-2006-07-21-0000015.1.1.0.dicom

308604

F1587945

99000002-2006-07-22-0000016.1.1.0.dicom

308604

FCC92241

99000002-2006-07-23-0000017.1.1.0.dicom

308604

F84614BD

99000002-2006-07-23-0000018.1.1.0.dicom

308604

1EFAA012

99000002-2006-07-26-0000020.1.1.0.dicom

923006

37579834

99000002-2006-07-23-0000021.1.1.0.dicom

923006

F6AE81FF

99000002-2006-07-23-0000022.1.1.0.dicom

308604

0781858E

ReadMe.txt

35

16E91512

 

 


4.6             UKCTOCS Database Queries – Story 7

In order to correct the information in a Dicom file header a user needs to obtain information related to it from the UKCTOCS database. The following tests are concerned with confirming that this operation can been performed.

Note: The tests confirm the functionality required of story 7: “Looking-up information in UKCTOCS” by listing the records returned by a number of standard queries.

Names for VolunteerRef

fit.ActionFixture

 

start

osImageManagerLibFIT.QueryVolunteersDialog

 

enter

VolunteerRef

99000002

enter

Surname

 

enter

FirstNames

 

press

Query

 

check

Result

99000002,Stott,William Philip Quentin

VolunteerRef for Names

Setup the query - when a value is not specified the corresponding field is not used to filter the list of records returned

fit.ActionFixture

 

start

osImageManagerLibFIT.QueryVolunteersDialog

 

enter

VolunteerRef

 

enter

Surname

Stott

enter

FirstNames

William%

press

Query

 

check

Result

99000002,Stott,William Philip Quentin

 


 

ScanDates for VolunteerRef

Setup the query

fit.ActionFixture

 

start

osImageManagerLibFIT.QueryScanDatesDialog

 

enter

VolunteerRef

99000002

press

Query

 

Results – US Date Format

osImageManagerLibFIT.QueryRecList

AppointmentDate

3-31-2002

1-21-2005

1-22-2005

11-1-2005

7-1-2006

7-21-2006

7-22-2006

7-23-2006

7-25-2006

7-26-2006

7-27-2006

7-28-2006

Results – British Date Format

osImageManagerLibFIT.QueryRecList

AppointmentDate

31-03-2002

21-01-2005

22-01-2005

01-11-2005

01-07-2006

21-07-2006

22-07-2006

23-07-2006

25-07-2006

26-07-2006

27-07-2006

28-07-2006


5.          UAT Manual Tests

Manual tests are performed in the following areas:

·        Operation of the User Interface

·        Functional Tests

o       Masking Personal Details – Story 3

o       Save and Restore Image Mask – Story 6

Each test is run by following a script and recording the results. The results of these manual tests form the criterion for acceptance of the system.

 

Preparation

·        Use SQL Server Management Studio to remove records from image database

·        Delete all files from MaskFragments dir

·        Run install program      


5.1          Operation of the User Interface

 

File | Logon - URA-Admin, password

check title bar - "[URA-Admin- admin] .\SQLEXPRESS:osImage .\SQLEXPRESS:ukctocs - osImageManager vx.x.x.x [Not for Clinical Use)"

Tools | Database Admin - Open the DbAdmin dialog

Run script to Clean Image table (e)

Press button to create UAT files

Press button to run the UAT and check results displayed in browser - all pass

Close DbAdmin dialog

press logon button on Toolbar - check logoff

check title bar - "osImageManager vx.x.x.x [Not for Clinical Use)"

 

File | Logon - URA-Guest, password

Check that DbAdmin dialog is not available

Tools | Options

            automatically read after browse

            expect surname, first name

            import mode = found in directory tree

File | Import - browse and then read UAT images - all XXX

View | Select Image Records - by disk ref = UAT

Check Images appear in tree and are correctly displayed - 22 images listed

Select root item in tree

Favorites menu - check just 'add' menu item (disabled)

Select image item in tree

Favorites menu - check just 'add' menu item (enabled)

File | Export - check recover mask is disabled and export to output dir

File | Logoff - check tree is empty

 

File | Logon - URA-Operator, password

Check that DbAdmin dialog is not available

File | Import - browse and then read output dir - press View and check all anonymous

Close Import Dlg (without importing)

Help | Contents - check help file version is same as app

Close Help

press Help button on Toolbar - check help appears at contents page

Help | Index - check help appears at index page

Close Help

Help | Search - check help appears at search page

Close Help

Help | Release Notes - check release notes appear in browser and version is same as app

Close Browser

Help | Licence - View - check Cranfield licence appears

Close Licence dialog

Help | Support - Website - check http://www.codeplex.com/ospacs appears in browser

Close Browser

press Support button on Toolbar check http://www.codeplex.com/ospacs appears in browser

Close Browser

Help | About - check copyright details appear for ezDicomax

Close About dialog

Tools | Options

            automatically read after browse

            expect surname, first name

            import mode = organise by exam directory

close Options dialog    

press Options button on Toolbar - check changes are persisted

close Options dialog

View | Select Image Records - by disk ref = UAT

Check Images appear in tree and are displayed

check status bar - "22 images listed"

select items in tree - check image

press Import button on Toolbar to open Import dialog

Browse and then read DATA\Images - 10 images in exam Y2004\M02\D04\E0000001, 12 images in 2004\M02\D05\E0000001 and 1 image in 2004\M02\D05\E0000002 need correction

select 10 images in exam Y2004\M02\D04\E0000001

Press View Button and select different images from the exam, view header

Press Correct Button, press OK and Yes when prompted to allow duplicates - 10 images in exam Y2004\M02\D04\E0000001 appears in the images list

Close File Import

File | Logoff

 

File | Logon - URA-Admin, password

Open the DbAdmin dialog

Run script to Clean Image table (e) - result is -1,22

File | Import - browse and then read UAT images - 10 images in exam Y2004\M02\D04\E0000001 are ready to import and 12 images in 2004\M02\D05\E0000001 need correction

Press Correct Button

Select different images from the exam

Press QueryUKCTOCS - check all three types of query

Press View Image

Select an image in the exam with no errors

press OK

enter disk label - Test1

press import

Check Images appear in tree and are displayed

check status bar - image count = 22

select item in tree - check image is displayed

Favorites | Add - confirm selected image added to Favorites menu + Clear and separator item

select another item in tree - check image is displayed

Favorites | Add - confirm selected image added to Favorites menu + Clear and separator item

Favorites | [First image menu item] - check image is displayed

Favorites | [Second image menu item] - check image is displayed

Favorites | Clear - check just 'add' menu item (enabled)

 

Edit | Find - Volunteer Ref=99000002

select item in tree - check image is displayed

Edit | Delete - press Yes when prompted and check image dispears from tree

View | Select Image Records - by disk ref = Test1

check status bar - "21 images listed"

View | Toolbar - toolbar disappears

View | Toolbar - toolbar appears

View | Statusbar - statusbar disappears

View | Statusbar - statusbar appears

select item in tree - check image is displayed

View | Show dicom header - check header info is displayed

View | Show dicom header - check image is displayed

View | Refresh Image Tree

View | Clear Image Tree

View | Select Image Records - by volunteer - dialog appears

enter "99000002" and press OK

check 9 images for 99000002 appear in tree

press select image button on Toolbar - dialog appears

enter "98011111" and press OK

check 12 images for 98011111 appear in tree

 


5.2      Functional Tests

Masking Personal Details – Story 3 and 6

·        Continue from manual testing in s5.1

View | Select Image Records - by disk ref = Test1

check 21 images appear in tree

delete contents of  output dir

File | Export - check 21 files appear in list

select recover mask and select output dir, press Export

Tools | Options import mode = all found in tree

File | Import - browse to output dir and read

Check 21 files appear in Correction list all with -DN

Select file, press view button and check mask is recovered - name in header is still 'xxx'

Close import dilaog

delete contents of  output dir

File | Export - check 21 files appear in list

deselect recover mask and select output dir, press Export

File | Import - browse to output dir and read

Check 21 files appear in Correction list all with -DN

Select file, press view button and check mask is unrecovered

Close import dilaog

Logoff

File | Exit

        Cleanup

·        Use SQL Server Management Studio to remove records Test1 from image database (or alter script e)

·        Delete all files from MaskFragments dir
 
Appendix A: Description of the System Test Environment

 

 

A.1      Test PC Specification

Although the URA System would normally be deployed so that the user acceptance tests can be performed on a single PC:

·        Test PC – 1 GB RAM, 80GB Disk space, 1.5GHz processor (or greater)

o       Windows XP Pro SP2

o       Internet Explorer 6.0

The following components will be installed on the Test PC during the installation of the URA Software, if not already present:

·        Microsoft .NET 2.0

·        Microsoft SQL Express v9.0

·        MDAC

 

A.2      Directories created during Installation

During the installation of the URA software on the Test PC the following directories are created:

·        URA installation directory; c:\Program Files\URA

·        UAT Data directory; c:\Program Files\URA\Data

·        URA Database Scripts directory; c:\Program Files\ URA\DbScripts

·        URA Mask Fragments directory; c:\Program Files\URA\MaskFragments

·        UAT Output directory; c:\Program Files\URA\Output


Appendix A: Test Data Description

 

Data is used for the UAT functional tests is comprised of Dicom Files located in a directory structure as well as records in the osImage (Image) database and the UKCTOCS (Patient) database.

 

A.1      Directories Created by the Installation Program

After the installation program has been run in the System Test Environment the Installation Directory is created as:

·        C:\Program Files\Cranfield University\osImageManager

and the following directories are created with the Installation Directory as their parent:

 

Directory Name

Location from Installation Directory

Data directory

\Data

Database Scripts directory

\DbScripts

Mask Fragments directory

\MaskFragments

Output directory

\Output

 

 

 

 

 


A.2      Files Created during Setup for UAT

 

 







Filename

Patient Name (0010,0010)

PatientID (0010,0020)

StudyDate (0008,0020)

SOPInstanceUID (0008,0018)

1.2.410.200001.1.9900.1.2005053113

Comment

Test000

Will^Stott

99000002

20050121

0000000.1.1

Duplicate SOPInstanceUID

Test001.dicom

William^StOTT

99000002U

20050121

0000001.1.1

 

Test002

William^Philip^Quentin^Stott

99000002UU

20050121

0000002.1.1

 

Test003.dicom

Stott^W^^^

99000002UUU

20050121

0000003.1.1

 

Test004

^^^Will^Stott

99000002UUUU

20050122

0000004.1.1

colour

Test005.dicom

William^StOTT

99000002UUUUU

20050122

0000005.1.1

 

Test006

Will^Stott

99000002

20050122

0000006.1.1

 

Test007.dicom

Will^Stott

99000002

20060701

0000007.1.1

 

Test008

Wxxxx^StOTT

99000002

20060701

0000008.1.1

 

Test009.dicom

Will^Stott

99000002

20051101

0000009.1.1

 

Test010.dicom

Charlie^Petzold

9811111

20030223

0000010.1.1

 

Test011.dicom

PETZOLD^C

9811111

20030223

0000011.1.1

 

Test012.dicom

Dr^C^PETZOLD

98011111

20060123

0000012.1.1

 

Test013.dicom

Herr^O’osterwijk

98555552

20060123

0000013.1.1

 

Test014.dicom

Jimmy^Denning

98000003

20060123

0000014.1.1

 

Test015.dicom

B^Stott

99000002

20060721

0000015.1.1

Bad PatientName

Test016.dicom

W^Stott

99000001

20060722

0000016.1.1

Mismatch VolunteerRef

Test017.dicom

W^Stott

99000000

20060723

0000017.1.1

Unknown VolunteerRef

Test018.dicom

W^Stott

99000002

20060724

0000018.1.1

ScanDate not found

Test019.dicon

W^Stott

99000002

20060725

0000000.1.1 (Duplicate Test000)

Dup SOPInstance - colour

Test020.dicom

W^Stott

ABC

20060726

0000020.1.1

Bad VolunteerRef - colour

Test021.dicom

W^Stott

99000002

20060930

0000021.1.1

date not found - colour

Test022.dicom

B^Stott

ABC

20060727

0000022.1.1 (Duplicate Test000)

Combined errors

Test023.dico

Will^Stott

99000002

20050121

0000023.1.1

(File not found)

Test024

(renamed JPG file)

(File not found)

Table A-1 : Test File Content Summary

 


A.3      Directories Created during Setup for UAT

The files defined in table A-1 are copied into the following subdirectories of the ‘Data’ directory by the automated test program the installation of the URA software on the Apollo workstation:

o        Image\

§         Y2004M01

·         D03

·         D04

§         Y2004M02

·         D03

·         D04

o        E0000001

§         Test000 – Test0010.dicom

§         Test023.dico

·         D05

o        E0000001

§         Test0011 – Test022.dicom + Test023.dico

o        E0000002

§         Test024        //JPEG

·         D06

o        E0000001

o        E0000002

o        E0000003

§         Y2005M04

·         D02

§         Y2005M05

 


A.4      Records Created in UKCTOCS Database during UAT Installation

 

§         UKCTOCS Database Records - The following records will be created in the Artemis UKCTOCS database during the Setup for UAT (see Section 4):

Table A-2: UKCTOCS.Volunteers database table

V_VolunteerRef

V_Surname

V_FirstNames

99000002

Stott

William Philip Quentin

99000001

Scott

William

98011111

Petzold

Charles Henry

98555552

O’osterwijk

Herman

98000003

Denning

James Paul

98100000

Liberty

Jesse

01100000

Hunter

David Ewan

 

Note: V_VolunteerRef 99000000 is  a value for unknown VolunteerRef (PatientID) found in files – see Test017.dicom
Table A-3 : UKCTOCS.UltraScanResults database table

US_VolunteerRef

US_ScanDate

comment

99000002

01/21/05

Test000,001,002,003

99000002

01/22/05

Test004,005,006

99000002

07/01/06

Test007,008

99000002

11/01/05

Test009

99000002

03/31/02

 

98011111

02/23/03

Test010,011

98011111

01/23/06

Test012

98011111

01/01/05

 

98555552

01/23/06

Test013

98555552

03/15/05

 

98000003

01/23/06

Test014

99000002

07/21/06

Test015 – Mismatch name

99000002

07/22/06

Test016 – Mismatch VolunteerRef

99000002

07/23/06

Test017 – Unknown VolunteerRef

[no record]

[no record]

Test018 – Mismatch ScanDate (07/24/06)

99000002

07/25/06

Test019 – Duplicate SOPInstanceUID

99000002

07/26/06

Test020 - Letters in VolunteerRef

99000002

07/27/06

Test021 – Invalid Date

99000002

07/28/06

Test022 – all errors

 


A.5      Specification of Image table in the osImage Database

 

§         osImage.Image Records - No records will be created in the Artemis URA database during the Setup for UAT (see Section 4):

CaptureDate

StoredDate

StoredBy

DiskRef

VolunteerRef

DicomRef

DicomFile

DicomFileSize

MaskFile

Flags

Datetime

Datetime

Varchar 50

Varchar 50

int

Varchar 64

Image

int

Varchar 255

Varbin 10

Image table

Note: ‘UAT’ can only appear in the DiskRef field of records created during UAT.

 

 

 


Appendix B: FIT Result Summary

 

fit.Summary

 

 

End of document

 



[1] The UKCTOCS database on Artemis is an independent copy of the production database

[2] A series of U characters were added to PatientID by staff at GCRC as a tactical fix so that data could be imported into a Sonoview database without conflicting with existing records

[3] Initially the Volunteer Reference Number (PatientID) was seven digits long, but it was increased to eight digits in 2003. Although all entries in the V_VolunteerRef field of Volunteers tables are now eight digits long, the PatientID field in Dicom Files created prior to 2003 will contain just seven digits.