Eric Poiseau,

1
Connectathon Organization

• Eric Poiseau,
• IHE Europe Technical Project Manager
• INRIA

2
Plan

• Why are we here ?
• Who are we ?
• Roadmap to the connectathon
• Testing tools
• Configuration exchange
• Demonstration Scenario
• Diverse questions and answers

3
Why are you here ?
4
Why are we here ?

• Gold Stars
• Testing the implementation of the TF in products
• provide feedback to the technical committee
• provide users confidence on products
• Testing it in a controlled environment
• partners are here
• bugs easier to identify and fix during the
  connectathon
• Prepare IHE Demonstrations
• Build a community...

5
of computer geeks !
6
...enjoying a local brewed Beer
7
Who are you ?

• 75 companies
• 113 systems
• 5 domains (RAD, IT-I, CARD, LAB, PCC)
• RAD 85 systems
• IT-I 67 systems
• CARD 22 systems
• PCC 13 systems
• LAB 12 systems

8
Where are you from ?

• 83 France
• 63 Italy
• 34 Germany
• 10 The Netherlands
• 10 UK
• 7 Belgium
• 7 Austria
• 7 Spain

• 6 Sweden
• 5 USA
• 4 Denmark
• 4 Portugal
• 3 Switzerland
• 2 Canada
• 1 India

numbers based on contacts entered in the
registration forms
9
More on registration

• Please check the page
• Connectathon -gt Vendor Grouping This shows the
  list systems implementing the actors playing a
  role in each of the Integration Profiles.
• I am giving you some warning on some profiles
•  No actor 
• Registration is evolving many companies drop
  actors or IP as we reach the deadline for the
  logs
• Please be warned and do not complain at
  Connectathon

10
Profiles that we may NOT test

• Cardiology
• Cath and Echo we are missing an OP We should be
  able to find volunteers !
• Laboratory
• LCSD No Code Set Master
• LIR No OF
• POCT No POC Result Generator

11
Profiles that we can NOT test

• Radiology
• CPI No print server ! So hardcopy CAN NOT be
  tested !!
• NMI No Acquisition Modality
• PGP No Acquisition Modality
• Charge Posting some missing actors but should be
  able to do it or some of it.

12
Profiles that we can NOT test

• IT-Infrastructure
• EUA no Kerberos authentification server
• I could provide one !
• PSA No context Manager

13
Roadmap to Connectathon
Workshop
Connectathon
14
Roadmap

• Feb 6-7th Workshop
• Feb 10th Deadline for registration changes !
• March 1st Submission of Dicom Conformance
  Statements
• April 1st Deadline for submission of logs
• April 15th Deadline for Configuration Checking
• April 24-28th Connectathon

15
Registration Changes

• I do not want to handle any registration question
  after this week !!!!!
• Enough to do with the connectathon !

16
Registration Changes

• You have till the end of the week (Feb 10th ) to
  inform me of any changes in your registration.
• You should know !
• Be nice to your peers !
• Whats in Kudu is what counts at the connectathon
  !
• Invoices will be send to your company next week.
• You have to pay registration Fee before
  connectathon !

17
Possible changes in registration

• Thorough / Supportive
• You need to have participated to a previous
  connectathon with the actor/IP
• You need to send me pointer to a published IHE
  Integration Statement for the system tested at
  the connectathon.
• Supportive results reported using a ?
• Thorough results reported using a ?
• Removing a system
• If you had only one system... then you will have
  to pay the fees for the  participant workshop 
• Adding a missing actor / integration profile
• Removing an actor / integration profile

18
Then....

• You have to pay the registration fees !
• Reminders
• No profit for IHE Europe
• Fees pay for infrastructure and environement

19
Pre-Connectathon Testing
20
Why do we need test tools ?

• Reduce the number of systems to 80 because the
  room we have reserved for the connectathon is too
  small !
• The project manager is evil and he likes to make
  you suffer with buggy mesa tools !
• The project manager like to spend his night
  checking logs
• Prepare your systems for the connectathon !

21
Why do we need test tools ?

• Test tools prepare you for the connectathon
• Provides a minimum set of test to prepare your
  systems
• Tools are a benefit of participation
• As a participant you get them before the public
  release
• Tools are released to the public later on

22
Why do we need test tools ?

• Tests encourage you and your peers to read
  details of the Technical Framework
• You may find you do not agree with our
  interpretation of the TF
• You may not agree with the TF
• If you and your peers complete the tests, we can
  avoid a lot of wasted time at the Connectathon
• Thus we can prepare more complex demonstrations
  and do more complex connectathon tests

23
Test Coverage

• Test software do NOT cover all aspects of the
  Technical Framework
• Test software do NOT guarantee compliance with
  DICOM or HL7.
• All what it does, is provide a reasonable
  preparation for the Connectathon.

24
Mesa Testing
25
Rad Card IT-I (except XDS)
26
MESA Tools simulate your peers
Mesa Simulator Win32 / Linux / Solaris
System being tested Win32 / Linux / Solaris
MESA ADT, OP, IM/IA
TCP/IP Network

• MESA OS is independant of system under test OS
• Choosing NT, Linux or Solaris is a question of
  taste

27
Hardware/network requirement for testing

• One computer system can
• Support all of the MESA actors
• Can serve as the driver for any system under
  test.
• Only one computer required to test an IHE actor.
• It is impossible to test multiple systems
  simultaneously
• (sockets are not multi-threaded).
• You need to test separate systems serially with
  little or no reconfiguration.

28
Mesa test how to

• Where do I get the tools from ?
• http//ihe.univ-rennes1.fr/testing
• If youre logged in youll get the last release
• If not youll get the public release
• Who writes the tools ?
• MIR, Offis, NIST, U of Montreal, INRIA
• What if I find a bug in a tool ?
• MIR, Offis http//rome.wustl.edu/bugzilla
• NIST, INRIA, U. Montreal contact me !

29
Installation

• Make sure you follow the installation
  instructions provided by Steven Moore
• Do not try to install from the sources
• Sources are provided for information

30
Most common errors encountered

• Environment variables not set
• Mesa_storage files not installed
• Wrong version of Win32 Perl
• SQL server is not installed
• Database tables are not installed
• But also possible errors in the tools !

31
Recommendations for MESA Software

• We recommend that you install and test the
  software as soon as possible
• The authors try to make the installation process
  simple, but there will be some difficulties
• It is better to go through a round of
  installation now rather than waiting until the
  final/next release is available

32
MESA Test Interactions

• Most MESA tests are independent of other tests.
  You can run them in any order.
• Most tests overwrite common data areas. They do
  not overwrite the output of the evaluation
  scripts.
• This implies you should run a test and perform
  the evaluation before starting another test.

33
MESA Test Overview

• Each actor/integration profile has several tests,
  each test is assigned a number (101, 102, )
• 100 series tests are for the Scheduled Workflow /
  Patient Information Reconciliation
• Other series of tests are for different features
  of the Technical Framework (for actors or classes
  of actors)
• How to know what test your systems have to pass ?
  
• Check the web tool on your system page

34
General Test Instructions

• Start MESA servers on test machine
• Run an interactive perl script that leads you
  through the test scenario
• Run a second perl script that evaluates your
  messages
• Check the logs for errors and try to understand
  the problems
• Send output of evaluation script to Project
  Manager
• Please comment your logs if this is needed

35
Test logs return (2)

• Do not send logs if you know that they will be
  rejected.
• Check Bugzilla pages for information
• Ask for some help
• When error please explain the errors
• Upload form for log return
• Please mention if you are resubmitting old logs

New
36
XDS
37
NIST Toolkit
New

• Remote Registry and Repository hosted by NIST
• Sources can submit documents to the NIST server
• Consumer can query and retrieve documents from
  the NIST server
• Java tool to submit and query a registry
• Log browser for PM to check/help testers
• Soon Bill will release a tool for your to check
  your own logs !!

38
Laboratory Tools

• Not script for the moment
• Message validation software
• http//ihe.univ-rennes1.fr/HL7

39
Few numbers...

• 10 weeks gives 400 hours of work
• gt3000 logs are required
• 5 min per log file makes 250 hours
• 110 systems
• 1 hour on phone/email makes 110 hours
• That does not give me much time left for the
  rest
• Lab tools, connectathon preparation, webtool
  maintenance, test data,.

40
System Configuration / Information
41
System Information

• Dicom Conformance Statement
• Upload form
• Practical Information
• Power information
• Number of chairs
• Storage
• Special requirements -gt contact me
• Please provide this information before March 1st

42
Configuration Information

• Have your configuration ready and confirmed
  before the deadline (April 15th)
• I have assigned some default values
• If you change it your peer will have to change
  it also.
• How important is it ?
• Most of the time spend in doing a connectathon
  test is spend checking/changing the configuration
  parameters.
• More systems more choices of peers. Try not to
  be the bad guy.
• Q How to provide my configuration information ?
• Answer
• Q How to find my peer configurations parameters
  ?
• Answer

43
Configuration Information

• If you feel that there are missing parameters,
• this is highly probable. Let me know ASAP
• No confirmation will be understood as a
  confirmation!
• This means that your peers will configure their
  systems with information that may be erroneous !
• Configure your systems before arriving to the
  connectathon

44
ConnectathonLogistics
45
Network Information

• We will provide
• IP Addresses and Host file
• Local DNS (preferred to host file)
• Netmask
• Gateways
• Time Server
• Kerberized Server
• Mail Server
• LDAP
• XDS Repository and Registry

46
Network Information

• Intranet will be at least 100 Mb/s
• Internet will be at least 10 Mb/s
• Internet is used for convenience for email and
  communication of files with home based team.
• Internet access is not guaranteed
• You will get one drop per system
• It is your responsibility to bring a hub

47
Power Supply

• 240 Volts
• A power strips with 3-5 slots per table
• UK plugs do not fit to spanish outlets !!
• Are we not talking about interoperability !
• If you need more (or less) than 240 V, please let
  me know ASAP !

48
Tables and chairs

• About 130 tables
• One per system
• Please use the table that will be assigned to
  your system
• If your company brings 2 systems, they might not
  be close to each other !!!
• 2 sits per table !

49
Connectathon Test
50
Kudu

• Configuration and tests management
• Provides list of possible peers
• Provides test scripts and hints about
  verifications performed by referees.
• Provides log archiving utility
• Provides verification logging
• Provides information about  persistent objects 

51
ADT

• Each PID source actor will be assigned a range of
  pid to avoid confusion.
• Patient Identifiers are 6 digit identifiers that
  begin with a two-digit code that identifies the
  system producing the ID.
• Thus, if your prefix is 10, your Patient
  Identifiers will be in the range of 100000 to
  109999.

52
Digital Certificates

• The GIP-CPS will play the role of the
  connectathon PKI
• GIP-CPS will provide VALID certificates
• Server certificates for the ATNA profile
• Person certificates for the DSG profile
• GIP-CPS will provide 2 persons for the
  connectathon
• Q You have a system with services splitted
  among more than one machine ?
• A You need a certificate for each machine !

53
Digital Certificates

• Certificates to be used only for connectathon and
  demonstrations
• Certificates are not meant to be used in a
  production environment
• We provide no guidance on how to manage those in
  a clinical environment

54
Preliminary Schedule

• Monday
• am installation of your systems
• Systems delivery
• Check network access, correctness of
  configuration
• 1030 am start of testing (p2p)
• .
• Wednesday
• start of scenario testing
• Friday
• am very last tests
• pm packing
• Package pick-up

55
Peer To Peer Tests (P2P)

• You have to test with some peers
• You need to get at least 3 instances of a test
  verified per test
• We are planning on getting kudu to record testing
  at the transaction level !
• Peer are prioritized
• You can do more testing.

56
Peer To Peer Tests (P2P)

• Enhancement
• Use of a chat room for peers to communicate and
  keep track of the transactions.
• Use of log storage mechanism (cut and paste the
  logs in text file)
• Peer configuration parameters
• Peer system localization on room plan
• Test verification worklist !
• Other suggestions/ideas

57
Scénarii Tests

• Compared to last year
• Increased complexity
• Could combine RSWF, LSWF, PIX, RID, EUA, XDS
• Increased number of peers
• Will have a schedule, so will need you to be
  ready at the time of the test.
• Will have a list of difficulties to check.

58
Hints

• Switching peer should be an easy and rapid task.
• Try to avoid need of rebooting
• Try to avoid typing the peer configuration each
  time you need to switch.
• Have the procedure codes entered in your systems.

59
How can I fail

• I have not a single test verified by Wednesday
  evening !!!
• Once again, be concerned !
• I am spying my colleagues !!!
• I am not fair to the PM !!!

60
Special Cases

• You all are in a special case !!!!
• I have finished all my testing on Monday, shall I
  leave ????
• Print Server case
• I have 5 zillion tests to perform during the
  week, can we stay for another 2 weeks
• Register more systems
• Register fewer profiles/actors per system

61
Results

• Concerns only positive results
• Test failure are forgotten
• Matrix published in the following weeks

62
Reminders ??
63
Notes on ATNA

• ATNA A system shall implement ATNA for all its
  actors....
• XDS requires ATNA
• XDS-I requires XDS, and thus ATNA !
• As a secure node let me know if you do implement
  Reliable Syslog RFC-3195 ?
• Please take some time to correctly perform test
  11100 List Audit messages

64
Notes on XDS

• Embedded Repository
• Document Source and document repository that
• Cannot submit a document to an external
  repository
• Cannot accept a document from an external source
• This is legal !!!!!
• CP from SM to IT-I Committee
• For practical testing reason please identify
  yourself
• As soon as possible

65
More on XDS

• This is an IHE European Connectathon !
• IHE-I affinity domain
• IHE-F affinity domain (DMP context)
• We are not testing DMP !
• See document published by IHE-F

66
Diverse Issues
67
Communication

• Me to you
• Email (mailing list) Make sure someone from
  your company is registered on the list
• ihe-europe-2006
• News on IHE-Europe Web (RSS)
• Phone make sure you have given a phone number in
  the registration form !!!!
• You to Me
• Email
• Phone ---

68
Communication

• Protocol (are we not dealing with
  interoperability)
• Company
• System
• Operating system
• Actor tested
• Tool Version
• Any information about your context will help me
• Remember that you have an open credit of ½ hour
  per systems do not waste it !!!!
• Give me some time to jump into your train of
  questions !!!!!

69
Shipping

• Shipping information
• We will let you know in time.
• Storage
• We will have a space for storage
• If possible, for small boxes store in your room
• Security during the nights
• Security from the host

70
Connectathon Working hours

• Officially from 9 am to 6 pm
• Practically from 830 am till 630 pm
• I will kick you out of the room at 630 pm
• Note that Siesta is not on the schedule !

71
Pre-Connectathon TODO

• Check your registration (before February 10th )
• I do not want you to tell me during the
  connectathon   I have forgotten to sign up for
  PIR, I though. 
• Configuration information gathering (you to me)
• Dicom Conformance Statements
• Port numbers, URI, AE Titles.
• Configuration of your system (me to you)
• Before connectathon begins.so before shipping
• You need to configure your system
• With your peer information
• With the connectathon network information
• With the testing dataset
• Pre-connectathon Test Logs

72
Connectathon Check List

• Technical Framework
• Your system fully configured
• Network
• Codes, procedures, tables.
• Laptop to run Kudu
• Could be also used to sniff messages or service
  you system
• Power strip power cord extension
• Hub (preferred to switch)
• Calibration material for CPI profile actors
• Print Server and print composer

73
Barcelona Survival Kit

• Culture Gaudi
• Beer Estrella Damm
• Food
• Buttifara
• Pan Tumaca
• Cava
• Ask our Spanish Friends for more hints !

74
http//www.ihe-europe.org

• Kudu
• Integration Profiles in Technical Frameworks
• Cardiology
• IT Infrastructure
• Laboratory
• Patient Care Coordination
• Radiology
• Connectathon Results
• Link to Vendor Products Integration Statements
  Pages

75
(No Transcript)