<table width="700pt"> <body> <tr> <td> <H3>Special Instructions</H3>   <p>The messages generated by the Patient Identity Source must conform to the HITSP Constraints to the message content.  <p><strong>Note:</strong> HITSP TP22 applies constraints only to the PID and MRG segments of the PIX Feed Message. Additional content constraints are associated with the PIX Query Message and the PIX Response message contents. A spreadsheet containing the full list of constraints associated with TP22, can be found at <strong><a href="http://xreg2.nist.gov/hit-testing/Documents/Constraints/TP22_Patient_Identity_CrossRef_Constraints.xls">HITSP TP22 Constraints</a></strong>.</p>   <H3>Evaluation</H3>  <p>In order to verify the test, the monitor will: <li>Request the TP22 Patient Identity Source to show the HL7 PIX Feed message transmitted to the PIX Manager <li>Validate that the HL7 Feed message content conforms to the HITSP specified constraints </p>  <H3>Description</H3> <p>The goal of this test is to verify that the message generated by the Patient Identity Source conforms to the HITSP Constraints. </p> <p> The HITSP TP22 constrains the PIX Feed MRG Segment as follows: <li>MRG-1.4.2  Assigning Authority's Universal ID - Shall only contain ISO Object Identifier (OID)   <li>MRG-1.4.3 Assigning Authority's Universal ID Type - Shall only contain "ISO" Note: "ISO" is the code that means "OID"  <li>MRG-7.3   Middle Names - If more than one middle name is available, all available middle names shall be concatenated with separating spaces in this component      <p> The HITSP TP22 constrains the PIX Feed PID Segment as follows: <li>PID-3.4.2   Assigning Authority's Universal ID (R) - Shall only contain ISO Object Identifier (OID)   <li>PID-3.4.3   Assigning Authority's Universal ID Type (R) - Shall only contain "ISO" Note: "ISO" is the code that means "OID" <li>PID-5.3      Middle Names (RE) - If more than one middle name is available, all available middle names shall be concatenated with separating spaces in this component   <li>PID-11.1.1 Street or Mailing Address (O) - Though not required by HL7 standard, use of national postal service standardized values is strongly recommended   <li>PID-11.1.2 Street Name (O) - Though not required by HL7 standard, use of national postal service standardized values is strongly recommended   	 <li>PID-11.1.3 Dwelling Number (O) - Though not required by HL7 standard, use of national postal service standardized values is strongly recommended    	 <li>PID-11.2   Other Designation (O) - May be used for second line of Street Address   <li>PID-11.3   City  (O) - Though not required by HL7 standard, use of national postal service standardized values is strongly recommended   <li>PID-11.4  State / Province (O) - Though not required by HL7 standard, use of national postal service standardized values is strongly recommended    	 <li>PID-11.5  ZIP / Postal Code (O) - Though not required by HL7 standard, use of national postal service standardized values is strongly recommended   	 <li>PID-13    Phone Number (O) - Home - If repetition occurs, then first occurrence shall be the primary telephone number used for patient contact. <li>PID-13.5  Country Code (O) - Though not required by HL7 standard, use of international and national standardized values is strongly recommended. For Country Code, if no value is present, 1 assumed for United States and Canada   <li>PID-13.6  Area / City Code (O) - Though not required by HL7 standard, use of international and national standardized values is strongly recommended. For Country Code, if no value is present, 1 assumed for United States and Canada    	 <li>PID-13.7  Local Number (O) - Though not required by HL7 standard, use of international and national standardized values is strongly recommended. For Country Code, if no value is present, 1 assumed for United States and Canada   	 <li>Though not required by HL7 standard, use of the International Standards Organization Codes for Representation of Names and Countries, ISO-3166, is strongly recommended; available from:  American National Standards Institute  25 West 43rd Street, Fourth Floor  New York, NY 10036    <p>The HITSP TP22 does not further constrain the PIX Feed MSH or EVN segments   <h3><a id='6'>Additional Resources</a></h3> <p>The HISTP Interoperability Specifications and related documents can be freely obtained from <strong><a href="http://hitsp.org">www.hitsp.org</a></strong>.   </font> </td> </tr> </body> <table width="700pt">