EyeCare Preconnectathon Test Software

Notes on your Pre-Connectathon Test Requirements, Tools and Documentation

Systems participating in the Eye Care Connectathon are required to run a set of pre-Connectathon tests based on the actors/profiles you registered for. First find out which tests are required for your system, then access the tools and documentation you need. Here's how...

1. What is the general pre-Connectathon test process?
   1. You will find your required list of "test to do" in Gazelle. Each test contains a link to the test description containing instructions.
   2. You will locate the tools and documentation you need using the tables below. Most tools you can be accessed over the internet; a few tools you install & run locally in your lab.
   3. For most pre-Connectathon tests, you will exchange a message (defined in an IHE transaction) with a test tool. Some tests ask you to test an object (eg. CDA document, HL7 message, DICOM image) against a tool that evaluates its contents. The tool will evaluate the message or object and create a log file indicating 0 or more errors.
   4. Once you achieve an error-free log for each test, upload that log file into Gazelle.
   5. The Connectathon Project Manager will be monitoring your progress completing tests in the weeks prior to the Connectathon.
2. Specifically, what are my pre-Connectathon test requirements???
   1. Pre-Connectathon Test Requirements are available in Gazelle after the close of Connectathon registration.
   2. Requirements customized for your connectathon test system are in Gazelle under menu Connectathon-->Pre-Connectathon-->Pre-Connectathon Testing . This list of 'tests to do' is based on the profile/actors/options you have registered to test. This is also where you upload results/logs for pre-connectathon tests.
3. How do I find the test tool software and documentation I need???
   1. The answer to this question has two parts:
      1. First, review the Index to IHE Tools used in Eye Care below, which contains the location of the software & documentation for the available tools.
      2. Next, refer to the Pre-Connectathon Test Status table on this page. This will tell you which tools you need based on the profiles you are testing.
   2. Note that, unlike Connectathon tests, the pre-Connectathon test descriptions do not reside in gazelle itself. This is because IHE has several different organizations that contribute tools and tests. Each pre-Connectathon test in gazelle does contain a link to the external test descriptions.
4. How do I submit results (test logs) from my pre-Connectathon tests?
   1. Access gazelle menu Connectathon-->Pre-Connectathon-->Pre-Connectathon Testing
   2. Click on the link in the 'Number of tests to do' column.
   3. This displays the list of tests to do. You can filter the list using the drop-down menus at the top of the page.
   4. Each test has a number in the first column. Click on the globe icon to get the test description.
   5. Only the tests with 'R' in the Option column are required. Those marked 'O' are optional.
   6. Tests run with tool produce a log file, or you can create a screen capture, or provide a URL to the test result
   7. When you complete the test, click on the 'Return log file' link in gazelle.
   8. Upload your result. Change the status of the test from 'Running' to 'To be verified'. Then hit 'Save'.
5. When are my test logs due? - Friday, October 3, 2014.

Are these tests a requirement?

Occasionally we get questions like, "Do I have to complete pre-Connectathon tests in order to participate in the Connectathon?", or "What happens if I don't do my tests?"

Here is the guidance we give: IHE invests in tool development and gives you a set of pre-Connectathon tests because we believe that when you perform these tests, you will improve the implementation of IHE profiles in your product. The tools are useful during development as well as to confirm that your development efforts reached at least one point of confirmation. And, you will be ***much*** more likely to pass your tests during the Connectathon. Connectathon Managers review your pre-Connectathon test logs in advance of the event to assess your level of preparedness. The Connectathon is a fast-paced, rigorous engineering event; you don't have time to be in 'learning mode' during the event.

We hope that you are motivated to do your very best to prepare for the Connectathon by completing all of your pre-Connectathon tests by the posted deadline, but completing tests late is better than not doing them at all.

Are they a requirement if I am doing Supportive testing?

If you qualify to perform Supportive testing, pre-Connectathon tests are not a requirement (because you have completed them in a previous year). Note, however, that we do not remove these tests from your pre-Connectathon list of 'Tests do do'; some vendors still want to perform the tests as part of their preparation. If you choose to skip the tests, just mark their status to be 'Supportive' in gazelle so we understand your intent.

Index to Test Tools used in IHE Eye Care

This table lists the tools available for testing Eye Care domain profiles, along with links to the tool & documentation.
To determine which tool to use for the profile you want to test, please refer to the Pre-Connectathon Test Status table in the next section.

Tool	Type	Description	Tool Location	Documentation	Support
Gazelle External Validation Services, aka "EVS client"	Validator, web-based	The EVSClient is user-friendly interface hosted on the web which allows the user to access several validation services (DICOM, HL7, CDA, others).	EVS Client Front End	user guide	submit issues & questions to our Jira issue tracker
Gazelle Order Manager	Simulator, web-based	Is used to test the RAD-2, RAD-3 and RAD-5 transactions in the A-EYECARE and B-EYECARE profiles. Is a DICOM Modality Worklist SCP, emulating an Order Filler in A, B & C-EYECARE. Also emulates actors in other domains' profiles, including LAW and LTW profiles and some parts of the SWF & SWF.b profiles.	Order Manager	user guide	submit issues & questions to our Jira issue tracker
Gazelle Patient Manager	Simulator, web-based	Emulates the ITI-31 transaction for PEC & PES actors defined in the B-EYECARE and PAM profiles, and the ADT actor in A-EYECARE and SWF. Also used for the PDQ and PIX profiles	Patient Manager	user guide	submit issues & questions to our Jira issue tracker
Gazelle Proxy	web-based msg capture & validation	"Man in the middle": Used during connectathon to capture the messages exchanged between two systems and forwards them to the validation service front-end	Gazelle proxy	user guide, plus training provided prior to connectathon	submit issues & questions to our Jira issue tracker
MESA Tools	Simulator, install/run locally	Legacy tool for testing many workflow profiles in the Radiology, Cardiology and Eye Care domains. If you have used them in the past, you are welcome to continue testing with them. If you are new to connectathon, we recommend using the gazelle-based tools.	MESA Release page	Actor test plans	MESA tools support email list

Pre-Connectathon Test Status for Eye Care profiles

The table below identifies the status of pre-Connectathon tests and which tools are used to test each profile in the Eye Care domain.
To locate the tools and documentation, refer to the Index to IHE tools in the previous section.

Lynn Felhofer is the Technical Project Manager who oversees testing in this domain.

Profile	Status of pre-Connectathon tests	Tool to use / Notes
A-EYECARE - Advanced Eye Care Workflow	TESTS READY	MOD & AMI actors use the Gazelle External Validation Service for DICOM object validation. Use the Order Manager as a Modality Worklist SCP. ADT, DSS/OF & OP actors use the Gazelle External Validation Service to check the HL7 messages you send. DSS/OF & OP actors use the Patient Manager simulator to send ADT messages to you. Optionally, all actors can run the MESA Tools.
B-EYECARE - Basic Eye Care Workflow	TESTS READY	PES & PEC actors use the Patient Manager to test exchange of ITI-31 ADT messages DSS/OF & OP actors use the Gazelle External Validation Service to check the HL7 messages you send. MOD & AMI actors use the Gazelle External Validation Service for DICOM object validation. Use the Order Manager as a Modality Worklist SCP. No tools for Image Mgr, Image Display & PPSM actors.
C-EYECARE - Core Eye Care Workflow	TESTS READY	Patient Registration Source use the Gazelle External Validation Service to check the HL7 messages you send. Patient Registration Consumer use the Patient Manager simulator to send ADT messages to you. MOD & AMI actors use the Gazelle External Validation Service for DICOM object validation. Use the Order Manager as a Modality Worklist SCP. No tools to test scheduling. No tools for Image Store/Display actor
ECED - Eye Care Evidence Documents	TESTS READY	Use MESA Tools. Evidence Creators also use Gazelle External Validation Service for DICOM object validation.
ECDR - Eye Care Displayable Reports	TESTS READY	Use MESA Tools
EC-CHG - Eye Care Charge Posting	TESTS READY	use the Gazelle External Validation Service to check the HL7 message you send. Optionally, all actors can run the MESA Tools.
ECAS - Eye Care Appointment Scheduling		Appt Scheduler & Requester use the Patient Manager simulator to send ADT messages to you. No tools to test scheduling.
GEE - General Eye Evaluation	No test tools.	We have a pre-Connectathon test for Content Creator & Content Consumer actors to exchange pre-connectathon sample documents