<H3>Special Instructions</H3> This test should be driven by the Document Repository actor. You should know which documents have been stored in your system. Make an effort to find Document Consumers and ask them to retrieve a document from your system. This test can be grouped with other XDS tests and completed by a set of cooperating systems. It is broken out separately to provide flexibility. <p>You will need to seek out one or more Document Source actors to load your Document Repository with documents to be retrieved.</p>  <p>This test shall be run using ATNA TLS communication.</p>  <H3>Description</H3> <p>A Document Repository is a server that does not have a user driving the retrieve process; in fact, the retrieve is by definition initiated by a different system. In this test, the Document Repository is expected to actively seek out Document Consumers to make sure that Consumers retrieve documents. If the Repository is not pro-active, it is possible that the system will be ignored.</p>  <p>This test uses two different patients for retrieving documents. The first patient is to be determined by the systems involved; find a patient that has been registered by a Document Source. This is a good test of different Document Source actors.</p>  <p>The second patient is a specific patient. Use the patient FARNSWORTH^STEVE. The Document Consumer actor can tie this in with PIX and PDQ to create a longer workflow.</p>   <H3>Evaluation</H3> Connectathon monitor will observe the Document Consumer while it queries for and retrieves a document from the Document Repository. Monitor will observe logs or other information indicating the communication takes place using ATNA TLS communication.