<H3>Special Instructions</H3> <p>You need 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> <p>The goal of this test is to create one valid <strong>HITSP/C62 Unstructured Document Component, Version 1.0 or later</strong> and publish it in a location to make it easy for other participants to locate.</p>  <p><strong>Note:</strong> The HITSP/C62 requires a valid CDA document (header) with a nonXMLBody. For valid code sets and values use only coded values found in the <strong>HITSP/C62</strong> itself,  <strong>HITSP/C80 Clinical Document and Message Terminology Component</strong>, and the <strong>HISTP/C83 CDA Content Modules Component</strong>. </p>  <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>  <h3>Minimum Document Content Requirements</h3> <p>The minimum content that must be present in the HITSP/C62 document for any given use case is defined in the HITSP Interoperability Specifications and related documents; additional content is acceptable but cannot cause a parsing error.</p>  <H3>Evaluation</H3> <p>This will be evaluated with the HISTP Content Creator tests.</p>  <H3>Description</H3> <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> <p>For any of the coded values (allergies, medications, etc.) use only coded values found in the HITSP C62 and related documents (C83, C80). The document should contain between 3 and 5 legal coded values. Do not invent codes or  import other codes.</p> <ol> <li>These next steps refer to storing the 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>	</li> <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> <li>Capture the report generated by the NIST content validator that indicates the file has no errors.</li> <li>Name the document HISTP_C62_kudu.xml where <strong><em>kudu</em> </strong> is your Kudu system name.</li> <li>Upload your documents according to the instructions in the <em>Connectathon Images/CDAs/Objects</em> section of Kudu.</li> <li>Update the <em>Connectathon Images/CDAs/Objects Publication/rendering page</em> page to list your document/zip file.</li> <li>Find the Connectathon monitor or monitors responsible for HITSP C62 Document Scrutiny. Make sure they are aware your document has been placed into the Kudu tool.</li> <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> <p><em>Note:</em> There is no obligation to render the HITSP C62 document, but providing a local rendering will greatly facilitate review of the document by the HITSP Monitors.</p> 