Difference between revisions of "Thorough Supportive Connectathon Testing"
m (→FAQ) |
|||
| Line 31: | Line 31: | ||
'''Q: Which profiles are eligible for Supportive testing?''' | '''Q: Which profiles are eligible for Supportive testing?''' | ||
| + | |||
'''A:''' In general, profiles that are in Final Text and have had no signficant Change Proposals in the previous year are eligible for supportive testing. | '''A:''' In general, profiles that are in Final Text and have had no signficant Change Proposals in the previous year are eligible for supportive testing. | ||
| Line 36: | Line 37: | ||
'''Q: If a profile has been around for multiple years but is not yet Final Text, is it a candidate for Supportive testing?''' | '''Q: If a profile has been around for multiple years but is not yet Final Text, is it a candidate for Supportive testing?''' | ||
| + | |||
'''A:''' No. Only Final Text profiles are eligible. | '''A:''' No. Only Final Text profiles are eligible. | ||
'''Q: Are Connectathon fees the same for Thorough vs. Supportive?''' | '''Q: Are Connectathon fees the same for Thorough vs. Supportive?''' | ||
| + | |||
'''A:''' There is no difference in cost. Connectathon fees are based on the number of systems registered. Fees are not affected by the number of domains/profiles tested, nor by thorough/supportive. | '''A:''' There is no difference in cost. Connectathon fees are based on the number of systems registered. Fees are not affected by the number of domains/profiles tested, nor by thorough/supportive. | ||
'''Q: Is there any difference in the final results for Thorough vs. Supportive?''' | '''Q: Is there any difference in the final results for Thorough vs. Supportive?''' | ||
| + | |||
'''A:''' No. If a Participant successfully completes supportive testing, from a connectathon results point of view, it is equivalent to thorough. ie. the Connectathon sponsors publish Profile/Actor pairs that are successfully tested by a Participant organization in the [http://connectathon-results.ihe.net/ Connectathon results database]. There is no distinction between those tested as thorough vs supportive. | '''A:''' No. If a Participant successfully completes supportive testing, from a connectathon results point of view, it is equivalent to thorough. ie. the Connectathon sponsors publish Profile/Actor pairs that are successfully tested by a Participant organization in the [http://connectathon-results.ihe.net/ Connectathon results database]. There is no distinction between those tested as thorough vs supportive. | ||
'''Q: May companies update their IHE Integration Statement with these results?''' | '''Q: May companies update their IHE Integration Statement with these results?''' | ||
| + | |||
'''A:''' In fact, there is no link between Connectathon testing and IHE Integration statements. An organization can publish an IHE integration statement for its product without ever testing at a connectathon. | '''A:''' In fact, there is no link between Connectathon testing and IHE Integration statements. An organization can publish an IHE integration statement for its product without ever testing at a connectathon. | ||
Revision as of 14:58, 25 February 2014
Thorough / Supportive Testing Explained
What is Thorough 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. Thorough testing at the Connectathon consists of successful completion by a Participant of three instances of each peer-to-peer test with three different test partners, and one instance of each no-peer test assigned for the Actor and Profile(s) it is testing during the Connectathon.
An exception to the "three-instance" rule of Thorough testing is: In some profiles, there may not be sufficient registration to provide three different test partners for a test. In this case, the "three-instance" requirement is relaxed, and participants are required to test with each of the available partners, pehaps only one or two.
What is Supportive testing? Why would we do Supportive testing?
Participants who have successfully tested at a previous Connectathon may qualify to perform Supportive testing. The benefits of Supportive testing are:
- Participants are not required to perform pre-Connectathon tests for a supportive profile/actor pair (because you have done it in the past).
- Participants receive full Connectathon credit for testing (ie a "pass) if they successfully perform one instance of at least one test for an Actor/Profile combination. Of course, you may choose to do more than one. This frees you up to spend more time testing new profiles if you wish.
- Participants undertaking Supportive testing are also required to assist other participants testing that profile who need a partner even if you have already completed your 'one required test'. Connectathon Managers will coordinate this additional testing as necessary.
Who qualifies for Supportive testing?
In order to qualify for Supportive testing, 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.
How do we request to do Supportive testing?
Supportive requests are now made directly in gazelle (no more spreadsheet!) and must be complete by the close of Connectathon registration.
- After logging in, select menu Registration --> Manage systems
- Edit the system of interest
- Select the Profile/Actors tab.
- In the column Requested testing type, select Supportive for the corresponding profile/actor.
After registration closes, the Connectathon Technical Project Managers will review and approve your request based on the criteria in the previous section. If you don't meet the criteria, you will do Thorough testing.
FAQ
Q: Which profiles are eligible for Supportive testing?
A: In general, profiles that are in Final Text and have had no signficant Change Proposals in the previous year are eligible for supportive testing.
When you register for profile/actors in gazelle, those eligible for supportive testing will contain a dropdown list enabling you to select either Thorough or Supportive testing; otherwise N/A is displayed.
Q: If a profile has been around for multiple years but is not yet Final Text, is it a candidate for Supportive testing?
A: No. Only Final Text profiles are eligible.
Q: Are Connectathon fees the same for Thorough vs. Supportive?
A: There is no difference in cost. Connectathon fees are based on the number of systems registered. Fees are not affected by the number of domains/profiles tested, nor by thorough/supportive.
Q: Is there any difference in the final results for Thorough vs. Supportive?
A: No. If a Participant successfully completes supportive testing, from a connectathon results point of view, it is equivalent to thorough. ie. the Connectathon sponsors publish Profile/Actor pairs that are successfully tested by a Participant organization in the Connectathon results database. There is no distinction between those tested as thorough vs supportive.
Q: May companies update their IHE Integration Statement with these results?
A: In fact, there is no link between Connectathon testing and IHE Integration statements. An organization can publish an IHE integration statement for its product without ever testing at a connectathon.