Part II: 2010 NA Connectathon Participants

1. Part II: 2010 NA Connectathon Participants • Part II: What 2010 NA Connectathon Participants need to know: Connectathon Administrative & Logistics • Connectathon Process Overview & Timeline • 2010 NA Connectathon Registration • Testing Cycle Requirements • Q & A

2. Audience • New participants: • Engineers/Managers who need to make sure all tasks are completed to receive Connectathon credit • Engineers/Managers who want their application demonstrated at a showcase • Connectathon veterans will find this section a review of past years.

3. What You Need to Know • Connectathon reference documents on http://www.ihe.net/north_america/connectathon_2010_participants.cfm • Policies and Guidelines from Sponsors • Connectathon Fact Sheetfor Participants • Product Manager’s Fact Sheet • Distilled version of the Participant’s Fact Sheet –> what Product Mgrs should know • Connectathon Timeline • Your deliverables and deadlines from now to the Connectathon

4. Connectathon Process Overview • Read the existing and new profiles (now) • Register for Connectathon (required) • Register for demonstration (optional) • Interview with Project Manager (required) • Submit pre-Connectathon test results (required) • Submit your configuration (by system) • Test and cooperate with peers during the Connectathon

5. Timeline Connectathon! Sep Oct Nov Dec Jan Jun - Aug What do we want to do? Can we do this… - Goals - People - Budget - Commitment Register Interviews Pre-connectathon testing & evaluation Config entry Logistics: hotel, shipping , electrical, people

6. How do we manage? Gazelle • Web-based tool used to manage a connectathon • Register the systems you will test (profiles/actors) • Determine your testing requirements • Submit your pre-connectathon test results • Enter configuration for your system (ports/URLs…) • Submit your DICOM Conformance Statement • Register the people who will attend • Find your test partners • Manage your testing during Connectathon week

7. First - Decide what to test • A large organization (Siemens) will register multiple systems • MR modality • CT modality • XDS Registry • EHR system (in XDS land) • Smaller organizations will likely register a single system • There are base fees and per-system charges • Read the fine print in the sponsor’s Policies for all of the rules

8. Registration: Preparation • Read the Connectathon Policies & Fact Sheet • Pay special attention to what constitutes a system and how you group actors/profiles • If you do not understand the rules or the tool, contact a Project Manager before/during the registration period for clarification • If you get this wrong now, you will spend the next 3-5 months wasting your engineering time writing software you will not use • You will also not develop the software you need for testing or demonstration

9. Registration: Gazelle • Enter organization & system details • Enter info about marketing and technical contacts • Enter the individual system(s) you want to test • For each system, you enter the combinations of actors, profiles, and options that will be tested for that system

10. We Do Not Add Actors After Close • We immediately start making Connectathon plans after registration closes • Within a week of close, we will close off profiles that have poor subscription • Showcase decisions made on the basis of your registration • You cannot stand in the back of the room and then tell us in December you want to add something • Think of this as placing an order

11. Consequences of Placing a Wrong Order • At McDonalds, if you give the wrong order, they will take your food back, throw it in the trash and give you a new Happy Meal • At Macy’s, they will take your clothes back and put them back on the shelf • At a Connectathon, you may find that all potential partners abandoned their work and you have no one to test with • If you want our help in finding test partners, you have to give us an accurate estimate of what you will accomplish • Your engineers won’t know how much work they need to complete

12. Registration: Paperwork & Payment • Print Registration Form • Gazelle will generate PDF with list of systems and charge information • Print the form, sign it, send a check to the address on the form • The printed form and check must arrive by the close of registration deadline • Sponsors will generate an invoice at your request. Follow up with the sponsors (RSNA, HIMSS).

13. Project Manager Interview • First-time participants must schedule an interview in Sep/Oct with a Project Manager • Purpose: • Ensure your Connectathon registration is in order • There are limits on the number of actors/profiles you can register in one system • We are keeping people from signing up for too much and then failing everything • There are dependencies between profiles that get missed • This is an annual problem that requires attention • Ensure you understand the process & timeline • Ensure you can find pre-connecthon tests & tools • Answer your questions

14. Interview Preparation • Interview Form • A set of questions to ensure you have the information you need to succeed • Do you know what your manager signed you up for? • Do you know how to find your required pre-Connectathon tests? • Do you know where the tools are? • …. • Email completed form to Project Manager after you complete Connectathon registration

15. Registration: Showcase • Project Managers are aware of showcase demos, but do not manage them. • You need to contact your regional organization: • RSNA, AAO, HIMSS in the US • IHE Europe will delegate to national IHE groups: • IHE-France • IHE-Germany, and many others • There are separate fees. • There are separate rules. These rules are written by the regional organization.

16. After Registration • Now that your marketing department has committed the engineering group to this project… • The engineers should read the requirements/specifications in the IHE Technical Frameworks • Actually, you should do that before you register

17. Pre-Connectathon (MESA) Tests • Project Managers publish pre-connectathon unit tests you run in your lab using test tools we provide • These are part of the IHE process and a requirement for Connectathon participation • There is a published deadline for submitting positive test results (not that you tried, but that you successfully completed the tests) • Results are uploaded into Gazelle and graded by Project Managers

18. Configuration Information • Project Managers will assign fixed IP addresses to your computers • You will need to review configuration information in Gazelle (port numbers, DICOM titles, Web services URLs) and complete configuration • There is a published deadline for this • If you fail to do this, your test partners will consider your company a poor candidate for future collaborative work • You will waste much time during the Connectathon

19. Conformance Documents • DICOM systems require a DICOM conformance statement • Load this into Gazelle • IHE Integration Statements (optional): • Companies may load a link into Gazelle

20. Staff Registration • Use Gazelle to register individual staff members who will attend the Connectathon • Understand the rules for the number of staffers you can register before you trigger extra fees • There is a deadline for this • If you do not register staff members, no entry, no lunch, no testing, no kidding!!

21. Connectathon Summary • Week-long testing event • Required tests for each profile/actor • You execute each test with 3 peer systems • Connectathon monitors examine results • Cooperative efforts to debug problems and work towards success • Opportunity to find problems in products and in the profiles • Showcase demonstration practice

22. Connectathon Tests • Each system is given a list of tests to complete • For most of the week, you manage your own schedule and perform tests as you can manage them (in the order you choose) • For some parts of the Connectathon, the managers will assign specific partners or specific work for a time period • The event is a combination of scheduled events and open (not free) time

23. Setting Your Expectations • This is an engineering testing activity that you need to manage properly. • You might not complete testing for all registered profiles. • Some tests you run will not be examined by monitors • Sponsors do not guarantee you will complete your tests • At 12:00:00 on Friday, we turn off the management tools, and the event ends • Your engineers may need to remove actors/profiles during the week

24. Connectathon Output • An IHE web site that lists that you passed tests for actor/profile pairs • We do not publish failures or work you did not complete • You are not “certified” • We do not guarantee conformance • We do not imply you are better than your competitor because you registered for more work • Your ticket to participate in IHE demonstrations

25. Email Lists • There is one google-groups email list for Connectathon-related announcements from the Project Managers and sponsors • You can subscribe yourself and as many colleagues as you wish • ihe-north-america-connectathon-2010@googlegroups.com • XDS implementers ask questions and share tips: • ihe-xds-implementors@googlegroups.com • There will be several email lists for showcase discussions • Project Managers will work with sponsors to publish a list, but we do not manage those lists.

26. You Are Responsible … • You are responsible for all requirements for your actor/profile pairs. • There is a separate Webex presentation on how to interpret the Technical Framework. • We do not test systems where the participant wants to do half of the work. • You need to implement for an actor/profile pair to receive credit for that pair. You choose one or more actors in a profile (no requirement to implement all actors in a profile). • This is pass / fail. There is no partial credit.

27. Timeline revisited Connectathon! Sep Oct Nov Dec Jan Jun - Aug What do we want to do? Can we do this… - Goals - People - Budget - Commitment Register Interviews Pre-connectathon testing & evaluation Config entry Logistics: hotel, shipping , electrical, people

28. Questions? • Process + Domain Managment • Steve Moore: moores@mir.wustl.edu • Lynn Felhofer: felhofer@charter.net • Eric Poiseau: eric.poiseau@inria.fr • PCD Domain • Manny Furst: efurst@imp-tech.com • HIMSS Showcase • John Donnelly: jtdonnelly@intepro.biz