Revised instructions

For details on the profile, visit the MMRO-II-page.

Tester = Vendor being tested

Peer 1, Peer 2, Peer 3 = Other peers/vendors being tested against

Note re. 10: It is our understanding that several application cannot handle sagittal orientations. This is for your information and will not be a failure if your application cannot handle such orientations.

Try and combine combine patients in different ways. Say patient 2 from peer 2, patient 3 from peer 3 and patient 10 from peer 3. In all cases, make sure to at least use one patient with mixed modalities.

Preparation

1. Import images from patient 2,3,4,5,6,10

Testing For each imported patient, the Tester must do the following:

1. Register all images
2. (If possible, also create one contour on primary image set to aid the Registered Contourer Actor)
3. Export SRO (and RT Struct) back to PACS

Then for each peer:

1. Let Tester import images and registrations from peer (make sure to mix patients)
2. Verify visually that the registrations looks correct

Let each peer:

1. Let Peer import images and registration from one patient (make sure to mix patients)
2. Verify visually that the registration looks correct (also verify image orientation)

Preparation

1. Tester imports images and SRO for patient 2,3,4,10

Testing For each peer do the following

1. Tester shows it can read in and apply the registration
2. Tester shows it can display contours on both CTs using imported SRO

Preparation

1. Same as for Registrator
2. For each patient, contour on the one of the image sets
3. Export all contours to PACS

Testing

For each Peer:

1. Tester imports images, registrations and contours from Peer's corresponding patient
2. Tester shows it can read in and apply the registration
3. Tester shows it can display contours on both images (using registration above)
4. Tester draws contours on one of the images
5. Tester moves contours on to other images (using imported registration)
6. Tester exports these contours (now in other FoR than drawn) to PACS
7. Peer imports images and contours and displays them correctly (name, colour, shape, position)

Note that the creation of dose objects must not necessarily be done by a peer also being tested for this profile, e.g. in the case with a pure dose viewer.

Preparation (Not actually a requirement for the vendor being tested to pass the profile, but encouraged if possible to create the test data needed for testing)

1. Use 2,3,4 or 10
2. Create registration b/w primary and secondary image
3. Create contours, plan & dose on primary images
4. Export registration, contours & dose to PACS

Testing This is exactly the same as for Registered Display, but tester should also display ability to move dose using SRO

(suggestion from Håkan MacLean)

1. Have each Peer export any CT, MR, PET, REG, RT Struct and RT Dose from PACS
2. Have each Peer improt any CT, MR, PET, REG, RT Struct and RT Dose from PACS

IHE – Radiation Oncology
2013 Connectathon
MMRO Profile
Test Data and Procedure

The table below identifies the Vendor Products participating as Actors in the 2013 Connectahon.

1. Datasets shown in the table below are available for testing the Multi-modality Image Registration Profile
2. For each of these datasets, a total of eight instances have been created and stored in the archive(s). The Instance UIDs, Frame of Reference UIDs, Patient ID, and Patient Name of these instances have been modified to ensure uniqueness among the patients stored in the archive.
3. The Patient ID (PID) of these datasets is of the form MMRYYCxxvv, where YY is the year of the Connectathon, Cxx is the dataset number, and vv is the vendor product code (see highlighted entries in the lefthand column of the vendor products table, above.
4. The vendor product code identies the vendor/product of the Registrator Actor that registers each patient dataset.
   1. Registrator Actors are to retrieve and process only the datasets corresponding to their own vendor/product ID.
   2. Registered Contourer, Registered Display, and Registered Dose Display actors are to retrieve three or more datasets corresponding to others’ vendor/product IDs.

1. Successful import of the FFS, HFP, FFP datasets, correct display of the patient images, and the ability to register each pair of images (Registrator). The SRO created must be stored and correctly read by other actors (for the Registrator). Other actors must be able to read and display the registered datasets including the saved SRO.
   1. MMRYYC02 = CT-CT Phantom Scans (HFP)
   2. MMRYYC03 = CT-CT Phantom Scans (FFS)
   3. MMRYYC04 = CT-CT Phantom Scans (FFP)
2. Successful import of the hybrid and non-hybrid datasets, correct display of the patient images, and the ability to register both the MR and PET images to the CT images.
   1. MMRC05 = CT-{MR,PET} Synthetic Scans (HFS), single FoR
   2. MMRC06 = CT-{MR,PET} Synthetic Scans (HFS), different FoR
3. Successful tests of non-archive actors for the Image Registration Profile will include at least the following datasets:
   1. It is our understanding that several application cannot handle sagittal orientations. This is for your information and will not be a failure if your application cannot handle such orientations.
   2. MMRYYC10 = CT,PET/CT,MR(HFS)

1. Registrator Actor
   1. Retrieve required image datasets corresponding to your own vendor-product code.
   2. Store Spatial Registration objects with Series Description indicating the vendor-product name of your Registrator Actor application and modalities registered.
   3. Save screen capture of your UI showing registration and upload to archive.
2. Registered Contourer Actor
   1. Retrieve required image series and Spatial Registration objects from patients corresponding to other vendor-products
   2. Store RT Structure Sets (in Frame of Reference of primary image series) with Series Description indicating the vendor-product name of your Registered Contourer Actor.
3. Registered Display Actor
   1. Retrieve required image series, Spatial Registration, and RT Structure Set objects from patients corresponding to other vendor-products
   2. Save screen capture of your UI showing registered display and upload to archive.
4. Registered Dose Display Actor
   1. Retrieve required image series, Spatial Registration, RT Structure Set , and RT Dose objects from patients corresponding to other vendor-products.
   2. Save screen capture of your UI showing registered display and upload to archive.

1. All derived data (Spatial Registration objects and RT Structure Sets) must be stored in the MOSAIQ (primary) archive.
2. Derived data should also be stored in secondary (Candelis, Velocity) archives.
   1. At least 3 vendor/product’s datasets for each transaction should be retrieved from each secondary archive
   2. At least 3 vendor/product’s datasets for each transaction should be stored to each secondary archive

1. Demonstrate ability to load each of the datasets as described above and perform a spatial registration.
2. Store the resultant spatial registration object.
3. If possible, store a second spatial registration (with appropriate noting) with a known offset (may be visually determined) for testing of subsequent actors.
4. (Optional) Demonstrate the ability to read in a spatial registration object from 3 vendors and verify / modify the spatial registration.
5. (Optional) Demonstrate the ability to store an image dataset. (If image data set is resampled, this transaction is not optional.)

1. For at least 3 vendors (not including identity) read in the image dataset pair, a spatial registration, and a structure set (can initially be a patient w/o structure set, but must demonstrate ability to read structure sets to pass this test).
2. Display the results. For the structure set, display the contours on both image data sets. This will be compared with the original spatial registration.
3. Generate contours on the secondary image dataset. Display the contours on the primary dataset. Store the contours in a structure set using the Primary Frame of Reference.
4. Read in an offset spatial registration and display (confirms that the original spatial registration is being used).

1. For at least 3 vendors (not including identity) read in the image dataset pair, a spatial registration, and a structure set.
2. Display the results. For the structure set, display the contours on both image data sets. This will be compared with the original spatial registration.
3. Read in an offset spatial registration and display (confirms that the original spatial registration is being used).

1. For at least 3 vendors (not including identity) read in the image dataset pair, a spatial registration, a structure set, and a dose object.
2. Display the results. For the structure set and dose object, display the contours on both image data sets. This will be compared with the original spatial registration.
3. Read in an offset spatial registration and display (confirms that the original spatial registration is being used).

1. For each transaction, demonstrate that data from 3 vendors (not including identity) can be received and stored without modification. This will be accomplished by sending the data to the archive and to the ATC SCP. The data in the archive will then be retrieved and compared at the ATC system for one of each transaction.
2. For each transaction, demonstrate that data from 3 vendors (not including identity) can be sent without modification of the original data. This will be accomplished by sending the data from the archive to the receiver and to the ATC SCP. The data at the receiver will then be retrieved and compared at the ATC system for one of each transaction.