Week of April 30th 2012

• Review Multiple Affinity Domain assignement
• Attend or view recording of the webex that will take place on Friday (TLS, Proxy, OrderManager) : See announcement on ihe-europe-2012 google group
• Make sure every participants to connectathon is recorded in the page : See Gazelle Test Management : Registration -> Testing Session Participants. Person with no badge will not be able to enter the room. Person with no badge will not be able to have lunch !
  • We will invoice the extra participants later on.
    
• In Gazelle Test Management please start and complete the no peer test that can be done ahead of the connectathon so that we can start verifying and validating them.
  • BIR / ID : Still some slots for verifying the test ahead of the connectathon (note that this single test (BIR_Image Display)  requires at least 4 hours for the verification).
  • MOD, RC, EC, CONTENT_CREATOR:  Please run the tests that asks you to create samples and enter them in Gazelle Test Management so that we can verify them.
    

Week of April 23rd 2012

• Modalities : we invite all of you to review the two following files and to check that in our list of codes we have codes that match your modality type (MR, CT, MG...). This will ensure that the Order Fillers and Order Placers will have procedures that match your system capabilities ready for Bern.
  • Ordering codes
  • Requested procedures
• BIR/ID : This week and next week we are performing webex sessions for evaluation of the test. Make sure that you have registered in the doodle for your systems (so far only one of your registered)
• OID Assignement : Many systems need OIDs as part of their configuration (Patient ID Sources, XDS Source & Repositories, others...). This year, these are assigned in gazelle under menu Configuration/OIDs for Current Session.

Week of April 9th 2012

• XDW : there is CP that will take into effect for the Bern CAT on that profile. The validation tool was updated accordingly. Please make sure to take it into account and revalidate your document already submitted in Gazelle for both Pre-CAT and CAT testing. Google Group on XDW is at : http://groups.google.com/group/ihe-xdw-implementors?hl=en
• No Peer Test : many of the no peer test for the connectathon ask you to provide some samples. Please start providing them in the sample section of Gazelle. You can then start the test instance, indicate the permanent link into the test instance and we will start to validate your sample. This will save YOU and US a lot of time in Bern.
• Proxy : We will use a proxy in Bern to capture the messages exchanged during testing. The use of the proxy is not required but strongly encouraged. Gabriel wrote a documentation of the tools that you will have in Bern, please read it : http://gazelle.ihe.net/content/proxy
• Order Manager : Connectathon veterans might remember a tool called the RisMALL. In Bern we will use a tool call the "Order Manager" that replaces the RISMALL and allows test participants to create and manage orders for the profiles in the LAB and RAD domain. A documentation of that tool is available. Please read it  : http://gazelle.ihe.net/content/order-manager
• We are planning webinars at the end of april and early may to exchange on this tools:
  
  • Gazelle usage during the Connectathon (1h) May 2nd at 10am CET
  • Proxy usage (1/2h) : May 3rd at 10am CET
  • Security tools usage (1/2h): May 3rd at 11am CET
  • Order Manager usage (1h): May 4th at 10am CET

Week of April 2nd 2012

• Start working on your CARNET ATA (http://en.wikipedia.org/wiki/ATA_Carnet)
• Start returning samples needed for your systems and if you need to render samples provided by your partner please render them and provide snapshot where needed.
  
  • We want to perform as much conformance testing of your samples before the connectathon starts. The idea to save monitor time and do all the conformance testing remotly. This will give you a chance to fix the problem that will be found in your samples, before the event.
  • So please visit the page Connectathon->List of Samples and return the samples requested and render the samples available providing a snapshot of the rendering by your application. This will inform your peer that you have done it.
  • Visit the page Connectathon -> Connectathon and review the list of "No Peer" test needed for your systems. Some of these test ask you to provide a sample, when you have done it, provide the permanent link to the sample in the test instance, mark the test as completed. This will trigger an event,  telling us that we need to verify your test.
  • Test marked as verified before Bern, will save all of us a lot of valuable time there.
  • Samples example : ATNA Questionnaire, Sample Images, Sample CDA Documents,...
• Continue registration of your participants to the event (15 companies have still not registered any participants yet). See the procedure here.
  
  • Please note that now adding extra participants will not give you extra tables (unless another organization drops participation and I have extra tables !)
• Continue pre-CAT test log return (see details below)
• Continue review of your configuration parameter (see details below)

Week of March 26th 2012

• IMPORTANT/URGENT : Last chance to get extra tables at the Bern connectathon by registering participants (individuals) to the connectathon.
  • you have till Friday March 30th at 5 pm to register the participants following the procedure described here
  • each registered system includes  2 participants
  • each extra 2 registered participants at 600 Euros you will get an extra table (see mail sent to google group for more details).
• Systems configuration have been initialized in Gazelle Test Management. So each of your systems have now configurations. Please review the configurations that have been assigned to you and edit them according to your needs. We have not yet assigned the OIDs. Will try to do it this week.
• Systems implement BIR/ID : I have contacted you individually per email. Please respond to that email about your status on testing. We need to setup conference calls to evaluate the test remotely and ahead of Bern.
• Continue working through your pre-Connectathon "Tests to do" list in gazelle. Test logs are due May 1st.

Week of March 19th 2012

• Continue working through your pre-Connectathon "Tests to do" list in gazelle. Test logs are due May 1st.
• I have finnished processing Supportive testing requests and registration changes request. Please check that your request have been processed and bug me if not.
• Access the digital certificates for TLS testing (ATNA profile). See the mail of Gabriel with the instructions

Week of March 5th 2012

• Continue working through your pre-Connectathon "Tests to do" list in gazelle. Test logs are due May 1st.
• Book hotel room for connectathon: See link here.

Week of February 27th 2012

• Get started on your pre-Connectathon tests. Upload successful results into gazelle.
• This is the last week to submit a request for Supportive testing. Please read details here.
• This is the last week for asking registration changes. Adding/Removing actors.

Introduction

This document provides policies and guidelines for organizations participating in testing at the IHE European Connectathon ("Participants") designed to help ensure successful testing.

Contacts

• Technical Manager
  
  • Eric Poiseau
• Administrative Manager 
  • Ben Celmata (Invoice, Contract)

Goals

Connectathon testing has three specific goals:

1. Testing Participant implementations of actors and profiles defined in the IHE Technical Frameworks

2. Testing and providing feedback on actors and profiles defined in the IHE Technical Frameworks
3. Preparing for any IHE demonstrations in which Participants may also be involved.

Participants are expected to support all three goals as appropriate, to work in a cooperative manner and to show respect for both their peers and the IHE testing process.

Registration

Online Testing Management System (Gazelle)

IHE uses an online testing management system, dubbed "Gazelle," to aid in organizing, conducting and recording the testing process. Prospective Participants begin the registration process by entering information in Gazelle about their organization and the systems they wish to test.

Participants are provided with secure access to their account in Gazelle. Throughout the testing process, they use it to access testing requirements and plans for their systems, to find and communicate with prospective testing partners, to track the successful completion of their testing activities and to receive other communications from the Sponsors and the Connectathon Management Team. Gazelle is also used by IHE Europe and the Connectathon Management Team to record and publish the results of testing. Participants are strongly encouraged to familiarize themselves in advance with Gazelle and to check it regularly throughout the testing process for announcements and other information.

Fees

Connectathon registration fees are based on the number of systems a Participant registers and the number of company/organisation representatives participating to the event. Fees for the IHE 2012 European Connectathon are:

1. Participation fees are proportional to the number of systems being tested. Participation Fee is 4200 Euros per system. This includes 2 company/organisation representatives at the connectathon.
2. There is no domain fee.
3. Registration of  additional company/organisation representatives if possible at the flat rate of 600 Euros for the entire event.
4. Registration of each 2 additional representatives entitles you to an extra table on site.
5. Registration of representatives need to be done at system registration time (before February 29th)
6. Registration of representatives after the deadline of January 15th will be possible at an higher rate.
7. All prices (in Euros) are subject to Belgium VAT at 21%  which can be reclaimed by your company.No VAT will be charge if you provide you Intra community VAT number and are a EU company
   
8. "If the performance of the Agreement by either Party or any obligation hereunder is prevented, restricted, or interfered with by reason of a Force Majeure, the Party whose performance is so affected, upon giving prompt notice in writing within fourteen (14) days after the occurrence of such Force Majeure to the other party and shall act to mitigate the damages caused by such Force Majeure, if possible. If a Force Majeure occurs, no Party shall be responsible for any damages, increased costs, or losses that the other Party may sustain by reason of such failure or delay in performance. The Party claiming Force Majeure shall be excused from such performance to the extent of such Force Majeure event, provided however, that the Party so affected shall take all reasonable steps to avoid or remove such causes of non-performance and shall resume performance of its obligations hereunder with dispatch whenever such causes are removed.Should these events of circumstances continue for more than three (3) months, each Party may lawfully and by registered letter terminate the Agreement, without any compensation to the other Party being due. "
9. Participation fees are non-refundable four (4) weeks after the end of the registration(a recovery of 50% of due fee can be submitted before the end of this period). The period of retraction is one (1) week. Participation fees will be invoiced following the registration.
10. Participation fees or purchase order are due by no later than January 31st 2012. An extra Late Payment Fee (12%) will be charged when payment has not been received on the IHE-Bank Account on February 5th 2012 or purchase order has not been provided.
11. The IHE Review Committee, reserves the right to refuse participation to systems containing combinations of Actors it deems to be inappropriate or not reflective of practical systems architecture. The IHE Review Committee will make this determination in consultation with the Project Management Team. Participants may be asked to revise their applications to limit the number and type of IHE Actors included in a single system.

WHEN & WHERE? Logistics, Timeline & Table Assignments

The 2012 European  Connectathon, IHE's week-long interoperability testing event, is held at the BernExpo congress center in Bern, Switzerland. We would like to welcome monitors on the connectathon floor at 9am on Monday May 21st. After you check in and get your monitor packet, we will meet with the monitor group at 10:30am for a 20-minute welcome/announcement session. You will find your table, get comfortable & connect to the network.  The testing starts at 11am. If you cannot arrive by 10:30am, don't worry, we will have people to help you get settled later than that. The testing schedule is:

• Monday 8:30-11am: Vendor arrival & setup
• Monday 11-5pm: Connectathon testing begins
• Tuesday thru Thursday 9am - 5pm: Connectathon testing continues
• Friday noon : Connectathon testing ends

TODO : Table Assignments

TODO : Connectathon floor plan

TODO : Network information

WHO & WHAT? Monitors' Profile Assignments

Monitor assignement can be found into Gazelle Test Management: click on Admin -> Manage Monitors

Find your name

• click on the magnifying glass to access the list of test assigned to you (do not worry there might be more than one monitor assigned to each test).
• click on the printer icon to generate a pdf with the description of all the tests assigned to you.

If you fill like you need to change the assignement contact Eric Poiseau or Anne-Gaëlle Bergé

HOW? Training Material

Manager Support

Contact these folks during the week if you have questions or problems. Support for specific tools is in the next section.

IHE Technical Framework Documentation

To prepare for the January connectathon, we recommend you read the chapter in "Volume 1" for the profiles you are assigned to evaluate. Each IHE domain's Technical Framework is segmented into multiple volumes; Volume 1 contains the use cases the profile addresses, the process flow and a diagram of the actors & transactions in the profiles. The technical details of the transactions are not in Vol 1, and as a monitor, you do not need to be an expert at that level. If you are reading a Trial Implementation Supplement, you will see that the contents are separated into Volume 1 and Volume 2 within the supplement.

If you are not familiar with IHE documentation, we recommend you view the "IHE Terminology" video in the training section above before you read the documentation.

IHE publishes its documents, organized by domain, on the Technical Framework page of ihe.net. We have created this index to help you find each profile: Summary of IHE Technical Requirements

FAQ for vendor participants

We have put together this FAQ page with answers to questions we frequently receive from our vendor participants. You may find it informative.

Contact Us

For help with logistics (travel, hotel, expenses), please contact office@ihe-europe.net
For questions about Connectathon processes & tools, or your assigment, contact Eric Poiseau.

Multiple Affinity Domain testing at the Bern Connectathon

XCA / XCA-I / XCPD Bern Testing Schedule

Testing of Cross-Community profile (XCA, XCA-I and XCPD) is directly organized by monitors during connectathon week. Unlike most connectathon tests, you will not choose your own partners. If you are doing cross-community testing, a monitor will visit you on Monday or Tuesday to explain the planning. In the meantime, you can review this document to review the planning document for cross-community tests: http://ihewiki.wustl.edu/wiki/index.php/File:XCA_connectathon_test_planning-Bern.doc

Explanation of Red/Blue/Green domains

This page applies to vendors testing XDS.b, XDS-I.b, PDQ/PDQv3, PIX/PIXv3, and XCA, XCA-I, XCPD.

If you're testing these profiles, please review this page during May.

In Bern, we will have 3 XDS Affinity Domains. Each of these domains is associated with its own Patient ID assigning authority. For ease of reference we call these the Red domain (1.3.6.1.4.1.21367.13.20.1000), the Green domain (1.3.6.1.4.1.21367.13.20.2000), and the Blue domain (1.3.6.1.4.1.21367.13.20.3000). We also have a 'local' Patient ID assigning authority (1.3.6.1.4.1.21367.3000.1.6).

1. Multiple-affinity-domains.ppt : This presentation gives you an overview of the 3-affinity-domain testing. Please review it prior to arriving in Bern!!
   
   
2. We have a tool for creating a patient with a Patient ID in the Red, Green or Blue assigning authority and sending it via HL7v2 or v3 to your test system: Gazelle patient generation & sharing allows you create & sending a single patient via HL7v2 & v3. It is also capable of resending an HL7 feed and batch sending of multiple patients.
   
   
3. Three-domain-assigning-authority-Bern.xls : XDS.b Registries and XCA, XCPD & XCA-I Gateways are assigned to one of the 3 affinity domains for the entire connectathon week.
   • Registries accept a patient identity feed, and register documents, with patient IDs in their assigned domain (ie with their designated Patient ID assigning authority)
   • Likewise, Gateway actors represent communities with documents in their one assigned domain.
   • PIX Managers, and some PDQ Suppliers, can operate across domains.
   • These assignments are in the table below and also in the excel spreadsheet linked in this item.

If you have questions about multiple affinity domain testing at the connecthon, ask Lynn Felhofer.