1. Connectathon Week Process: Monitors
Steve Moore
Lynn Felhofer
Please mute your phone
Send questions to Lynn via chat
She will:
Interrupt me
Answer you directly
Hold the question until later

2. Two-part presentation
Connectathon Testing Process
Gazelle ‘how to’ for Connectathon week
Plus, Q & A

3. Vocabulary Participant (500+) Peer / partner / test system (154)
Test (peer-to-peer & no-peer)
Test Instance
Connectathon results / “grading”
Staff / responsibilities
monitor
domain technical project manager
Paul (PCD), Lynn (ITI, Rad, Card), Steve (QRPH, PCC, HSP), Eric (Lab, Pharm, Path)
connectathon technical manager
Lynn, Steve, Eric
tool support

4. The Gazelle Dating Service
Each participant is shown a list of tests to run
The list is customized to the set of actor/profile pairs they implement
Each monitor is shown a work of tests to evaluate
The list is customized to your testing area
You will overlap with other monitors
It will be more clear during the Gazelle demo

5. General process for the week
Participant
Identify a test to run
Select a test partner; make arrangements to test
Start a test instance
Do the steps / gather evidence
Mark test ‘to be verified’
(3846)
Wait for a monitor / move on to other work
Domain Technical Project Managers:
Nightly “grading” (1304)
Manual process

6. Setting context: …what is a connectathon test?
IHE Conventions
Metadata (about the test)
Participants
Description
3 parts to the description
Steps
Files and Chat Window

7. Test Metadata

8. Test Description

9. Test Steps

10. Test Files and Chat

11. Test Participants

12. Test Status Values Set by participants: Set by monitors:
Running Verified
Paused Partially verified
To be verified Failed
Critical (thurs/fri)
Aborted (terminal state)

13. Miscellaneous but important notes
Who are valid test partners?
In general, one organization cannot have two systems acting as test partners
The whole purpose is to test with other participants
You will be asked how “Do we really need three partners”?
Do not answer this question.
Send them to talk to Lynn, Steve, Eric Poiseau, Paul Sherman
There is no “partial credit” on a test instance
You cannot pass system A and fail B.
For a test, all pass or all fail.

14. Miscellaneous but important notes
Once you claim a test, maintain ownership and finish evaluation
You might have to defer and come back
Do not claim someone else’s test unless you discuss with them
You might have observed something and want to follow up. Another monitor might not be aware.
Participants are required to be cooperative.
Noon on Friday is a dead stop
No results are accepted after noon Friday
No test instances are evaluated after noon Friday

15. Logistics Testing schedule Communication during the week: PUSH method:
Mon 9:00 Meeting, 10:00 – 5:30 Testing
Tues /Thurs 9:00 – 5:30 Testing
Fri 8:00 – 12:00 Testing
Communication during the week:
PULL method (aka: I need help!)
Now! – come and see Steve Moore
Not urgent -- send (expect an evening answer)
PUSH method:
No verbal announcements to the group
Twice daily news: 9am / 1:30pm

16. 2. Gazelle “how to”

17. Mini Proxy intro

19. Misc. tips & tricks User preferences Skype ID Find a monitor
Search box
Browser recommendation
Gazelle on a tablet

20. Monitor Resources Page