In order to successfully complete testing at the Connectathon and appear in the table of testing results published by the Connectathon Sponsors, a system must complete either Thorough or Supportive Connectathon testing.
1.Thorough Testing normally consists of successful completion by a Participant's system of three instances of each peer-to-peer test and one instance of each no-peer test assigned for the Actor and Profile it is testing. The list of required tests for each actor and profile is developed by the Connectathon Management Team and is published for each Participant in Gazelle.
- Exceptions to the three-instance rule of Thorough Testing are:
- The three instance requirement may be met by passing either three peer-to-peer tests or by passing two peer-to-peer tests plus successful participation in a group test. Success in demonstration testing may also, at the discretion of the Connectathon Managers, be counted as one instance of successful peer-to-peer testing.
- Any test identified as a no peer test within the Gazelle testing management tool requires only one observed instance to constitute successful testing. Examples of such tests are: "load data onto the Central Archive" and "perform system calibration."
- Testing in profiles with few actors: In any profile where not enough systems are registered for particular actors to enable corresponding systems to satisfy the three-instance requirement, that requirement will be relaxed. In cases where fewer than three, but at least one instance of each actor required for thorough testing of a profile is subscribed, Participants will be required to test with each of the available actors. Successful testing with all available actors will be reported in the published table of Connectathon results.
In any profile where no systems are registered for one or more of the required actors, testing will not be performed. The Sponsors and Connectathon Management Team will inform Participants registered to test other actors in such a profile following the close of registration.
2. Some systems may qualify to perform Supportive Testing. In this category of testing, Participants receive credit for testing if they perform one observed instance of at least one test for an Actor/Profile combination. Participants undertaking Supporting Testing for a given profile are also required to assist other participants testing that profile who need a partner. Connectathon managers will coordinate this additional testing if necessary.
After Connectathon registration closes, organizations may request the Supportive Testing option. Systems that qualify for Supportive Testing are not required to complete the pre-Connectathon tests. In order to qualify for Supportive Testing of a system, a Participant:
- Must previously have passed Thorough Testing for that particular Actor and Profile at a Connectathon whose results are reported in the IHE database at http://connectathon-results.ihe.net/
- Must also have published an IHE integration statement in the IHE Product Registry (http://product-registry.ihe.net/) for that actor/profile.
- Supportive Testing will not be allowed where significant revisions have recently been made to the Profile in which the participant is testing. The Connectathon Managers will provide participants with a list of such profiles.
Applying for supporting testing
NEW PROCESS, READ CAREFULLY !
Steps to request Supportive testing :
- Log into gazelle test management
- Goto Registration -> Manage systems
- Edit the system of interest
- In the column "Requested Testing Type" select supportive on the row corresponding to the actors/profile/options for which you are requesting supporting testing.
- The project manager will check that your company has a product declared in the Product Registry for the corresponding actors/profile/options. If not your request to be supported will be rejected.
Only the actors/profile/options that are eligible for the supportive mode contains the list box. For the other ones the column shows N/A : Not Applicable.