<H3>Special Instructions</H3> This test is only for systems which support the <b>Zip over Email</b> Option in the XDM profile. <p>For the purpose of XDM testing at the connectathon, the Portable Media Importer will create an email account and share the email address with the Portable Media Creator. This can be a gmail account, for example. If the systems support the <g>Zip over Email Response</b> option, the PMC would need to have an email account as well.</p> <p>A spreadsheet illustrates the options supported by XDM Portable Media Creator and Portable Media Importer systems in the Feb 09 NA Connectathon, as well as the IHE Content profiles supported by the PMC actors who are creating XDM media.</p>  Access the <a  href=http://ihewiki.wustl.edu/wiki/index.php/North_America_2009#Feb_23-27.2C_2009:_Connectathon_Week_Survival >'partners' spreadsheet</a>.   <p> The Importer system must find a Portable Media Creator who supports content that you support, and is required to  demonstrate some form of 'processing of medical data' in the types of documents  it is designed to support.</p>   <p> You may want to run tests <b>XDM_Audit_Export</b> and <b>XDM_Audit_Import</b> at the same time. </p> <H3>Description</H3> This test case is used to create XDM-formatted media in a ZIP file and send if via secure email per the XDM profile. <H3>Evaluation</H3> <p>The Connectathon monitor will visit the <b>Portable Media Creator</b> system and watch it create a zip file.  Before it is sent via email, verify:</p>  <ol> <li>README.TXT is present at the root level in the ZIP file.   The README.TXT will contain <ul> <li>Contact info on the institution that created the media <li>Information regarding the application that created the media <li>Contact information of the vendor of the application that created the media <li>General information about the overall organization of the media  <li>(optionally, if a Media Viewer is contained) OS supported; name of the product application and software version; contact information of the vendor that provided the Media Viewer; disclaimer about the intended usage of the application; list of minimum requirements  </ul> <li>INDEX.HTM is present at the root level and contains properly formatted XHTML.  This file will contain: <ul> <li>Patient ID and demographics (submission sets on the media may belong to one or more patients) <li>Source Facility information </ul> <li>The root directory contains a folder IHE_XDM.  <li>IHE_XDM folder contains one or more subfolders for the contents of the submission sets.  <li>The subfolder(s) each contain the file METADATA.XML  <li>The subfolder(s) may contain  <p>- one or more files  that are the single-part document(s) referenced by the METADATA.XML  </p> <p>- one or more sub-directory for each multi-part document </p> <li>File names are restricted to eight characters with a three-character extension, upper case letters, numbers and underscore; maximum depth of directories is eight. <li>The submission set(s) contain one or more samples of each IHE content profile the Portable Media Creator system supports. </ul> </ol> <p>Then the connectathon monitor will observe the zip file being sent as an email attachment to the PMI.  You can verify the secure email settings in the email set up on the PMC.</p> <p>Verify that the email:</p> <ol> <li>is secured by S/MIME</li> <li>is encrypted using AES</li> <li>is digitally signed by the PMC system</li> </ol>   The Connectathon Monitor will then visit the <b>Portable Media Importer</b> system to verify that: <ol> <li>The email is received.  The subject line of the email must contain <b>"XDM/1.0/DDM"</b>. <li>It is able to successfully retrieve the email and open the zip file attachment. <li>Supported documents are successfully imported into the system.  The operator of the Importer system may demonstrate this by various means, eg displaying the imported document (after the media has been removed from the system); displaying contents from the imported file(s) in the system's database <li>The Importer system can demonstrate some form of 'processing of medical data' in the types of documents it is designed to support.  Ie it is not sufficient to just write the imported document to the Importer system's hard disk. <li>Referring to the spreadsheet in the 'Special Instructions' section, the Portable Media Importer must demonstrate successful import and processing for each supported document type. <li>The Importer has a method for verifying the integrity of the media by comparing the size and hash values of the entries in METADATA.XML to the relevant submission set directory(ies).   </ol>  <p> Finallly, if both systems support the <b>Zip over Email Response</b>, the connectathon monitor will verify on the PMC that it received an acknowledgement email indicating success.  The error case is not tested here.</p>    