<h3>Special Instructions</h3>
 None
 <h3>Description</h3>
 <p>
 TCE_Export tests the entire teaching file /clinical trial export chain from Export Selector to Receiver.
 </p>
 <p>
 The <b>Export Selector</b> should choose three set of objects that will be exported in three separate transactions:
 <ul>
 <li>At least one of those sets of objects should span multiple studies, if the workstation allows it.  
 <li>If selection from multiple studies is not allowed, then at least one set should include objects from multiple series, if the workstation allows it.   
 <li>Also at least one of the sets should include non-image objects (e.g. reports, GSPS objects) in addition to image objects, if such other objects are available.  The set with non-image objects may be the set that includes objects from multiple studies.  </ul>
 The <b>Export Selector</b> should be configured to allow the tester to select or enter a different observer name and a different description for each of the exported sets of objects.  The observers for the three sets of objects shall be:
 <ol>
 <li>Fine^Larry</li>
 <li>Howard^Curly</li>
 <li>Howard^Moe</li>
 </ol>
 The description for the three sets of objects shall be:
 <ol>
 <li>Departmental Cases</li>
 <li>Research Cases</li>
 <li>Personal Cases</li>
 </ol>
 The manifest for the second set of objects (the ones with Curly as the observer with the description "Research Cases" should have the title (TCE002, IHERADTF, 'For Clinical Trial Export').  At least one of the other two cases should have the title (TCE001, IHERADTF, 'For Teaching File Export').
 <p>
 If an <b>Export Manager</b> is available for the test, the Export Selector shall route the objects and manifest to the Export Manager.  If no Export Manager is available, then the Export Selector will send the images directly to the Export Receivers.
 </p>
 <p>
 The <b>Export Manager</b>, if present: 
 <ul>
 <li>will be configured to route the set of objects to three different destinations.  
 <li>It will select which destination to send the objects to based on the observer and/or the description in the manifest.  
 <li>The Export Manager will de-identify the objects for Larry and Curly prior to fowarding them.   
 <li>If the Export Selector supports the <i>De-identify Pixel Data Option</i>, this will be demonstrated for the Connectathon Monitor.
 <li>The Export Manager will be configured to not de-identify the object for Moe.
 </ul>
 </p>
 <p>
 Up to three Receivers can participate in this test.  Each receiver will be a different destination configured in the export manager.  If three Receivers are not available, then the routing in the Export Manager will be configured to send to as many receivers as are available, with some receivers doing double or possibly triple duty.
 </p>
 
 <h3>Evaluation</h3>
 <p>
 The Connectathon Monitor will check:
 <ul>
 <li>that each set of objects arrives at the appropriate Receiver, based on the observer and/or description</li>
 <li>each manifest contains instances from only a single patient
 <li>for the RAD-52 transaction (additional objects added to set 1), the Document title is TCE0006 IHERADTF, 'Additional Teaching File Information'
 <li>that the objects (for Larry and Curly, but not Moe) were properly de-identified</li>
 <li>If the Export Receiver does not support all SOP classes referenced in the manifest, then the transfer will partially or completely fail
 </ul>
 </p>
 
 