<a href="#1">Description</a><br> <a href="#2">Minimum Document Content Requirements</a><br> <a href="#3">Submission of Test Files for Evaluation</a><br> <a href="#4">Evaluation</a><br> <a href="#5">Special Instructions</a><br> <a href="#6">Additional Resources</a><br><br>  <h2><a id='1'>Description</a></h2> <p>The goal of this test is to create one valid <strong>HITSP/C78 Immunization Document Component, Version 1.0</strong> and publish it in a location to make it easy for other participants to locate. This posted copy will also be used by the HITSP test monitors to verify results; see the steps below for submitting your content file.</p>  <h2><a id='2'>Minimum Document Content Requirements</a></h2>  <p>The HITSP/C78 requires Level 2 encoding (section-level codes). For valid code sets and values (allergies, medications, etc.) use only coded values found in the <strong>HITSP/C78</strong>, <strong>HITSP/35 EHR Lab Result Terminology Component</strong>, <strong>HITSP/C80 Clinical Document and Message Terminology Component</strong>, and <strong>HISTP/C83 CDA Content Modules Component</strong>. Do not invent codes or  import other codes.</p>  <p>The minimum content that must be present in the HITSP/C78 document for any given use case is defined in the HITSP Interoperability Specifications and related documents; unless specifically prohibited by the specifications, additional content is acceptable but cannot cause a parsing error.</p>  <p>For any of the coded values (allergies, medications, etc.) use only coded values found in the HITSP/C78 and related documents (C35, C80, C83).</p>   <p>Each Content Creator has been assigned one well known patient (see test Content_Creator_Demographics) with a Patient ID in the proper domain. Create a document that uses the demographics for this patient and patient ID (if possible).</p>   <h2><a id='3'>Submission of Test Files for Evaluation</a></h2>  <p>These next steps refer to storing the completed document and reference information in the Kudu tool. You will find the page in the Kudu tool by selecting Connectathon and then Connectathon Images/CDs/Objects. The link to that page is <em><a href="system_con_object.php">Objects Information</a></em></p>  <ol> <li>Name the CDA XML document that is being tested <strong>HISTP_C78_kudu.xml</strong> where <strong><em>kudu</em> </strong> is your Kudu system name.  <ul><li><em>Note:</em> There is no obligation to render the HITSP C78 document, but providing a stylesheet for local rendering will greatly facilitate review of the document by the HITSP Monitors.</li></ul> </li><br>  <li>Validate the document against the NIST validation tools until the report indicates the file has no errors for the sections under review</li><br>  <li>Capture the report generated by the NIST content validator, save as <strong>HISTP_C78_kudu.htm</strong> where <strong><em>kudu</em> </strong> is your Kudu system name.</li><br>  <li>Create a zip file that contains both the test file and the report (and stylesheet if available) named <strong>HISTP_C78_kudu.zip</strong> where <strong><em>kudu</em> </strong> is your Kudu system name.</li><br>  <li>Navigate to the <em><a href="system_con_object.php">Objects Information</a></em> page within Kudu.</li><br>  <li>Enter the Patient ID, Patient Name, company name, your name, and your Kudu system name into the description of the <em>Connectathon Images/CDAs/Objects</em>.</li><br>  <li>Upload your zip file according to the instructions in the <em>Connectathon Images/CDAs/Objects</em> section of Kudu.</li><br>  <li>Update the <em>Connectathon Images/CDAs/Objects Publication/rendering page</em> page to list your document/zip file.</li><br>  <li>Notify the Connectathon monitor or monitors responsible for HITSP C78 Document Scrutiny. Make sure they are aware your document has been placed into the Kudu tool and is ready to be reviewed.</li><br>  <li>If you support XDS or any other pre-requisite, complete any test that requires you to store and register your document with a repository/registry. You do not need to complete that XDS store step in order to complete this test.</li> </ol>    <a id='4'><H2>Evaluation</a></h2>   <p>This will be evaluated with the HISTP Content Creator tests.</p>  <p>The evaluation will consist of a review of the NIST validation report for the submitted file. Where there are additional content requirements, the file will be reviewed to ensure the proper content is present. This may be via an inspection of the raw text, or via a stylesheet.   <h2><a id='5'>Special Instructions</a></h2>  <p>You are encouraged to complete this test by Day 1 at 17:00. If you complete after Day 1, you increase your risk that Content Consumers will ignore your document, and you will be marked incomplete.</p>   <h2><a id='6'>Additional Resources</a></h2>  <p>The HISTP Interoperability Specifications and related documents can be freely obtained from <strong><a href="http://hitsp.org">www.hitsp.org</a></strong>. Example files, schematron rules, and other support documents, as well as a web-service interface to the validator, can be found at <strong><a href="http://xreg2.nist.gov/cda-validation/index.html">CDA Guideline Validation</a></strong> site.</p>  