NA 2009 Connectathon Support

1. NA 2009 Connectathon Support Description of Services Provided for Connectathon Participants

2. Connectathon Uses Private IP Space Computers Inside Connectathon – Private Address Space Router / Firewall / NAT Internet

3. Private Address Space • Each computer receives a private address • Fixed IP address for a system involved in testing. Most will be wired; some PCD members will have wireless + fixed IP • DHCP for support systems (laptop to read email, use Kudu). This can be on the wire or wireless • No restriction on outbound • Some computers can have public IP addresses managed at the router. • This supports inbound traffic • Only request if you need it. We have limits on the number of public IP addresses

4. Color Key for Next Slides System provided by Project Managers and/or HIMSS demonstration. Required for testing. System provided by Project Managers or NIST to test a new feature. This is optional for 2009; may be required in 2010 Tools provided by NIST that are part of the test apparatus. Separate color for proper credit. This would be you.

5. These Systems are at the Connectathon Kudu DNS Server SMTP Server RIS Mall HIMSS Registration NIST Registry SyslogProxy XDS Proxy HL7 V2 Proxy V2 –> V3 Gateway Gazelle Test Engine DICOM Central Archive CPI Calibration Tools Participant 1 Participant 2

6. Kudu • IP: • Will give you • List of tests to run • Your link to peers • Link to some test objects as samples (CDAs) • Your report of what actor/profiles are complete

7. DNS Server • IP: • Will provide the private IP addresses of systems registered in Kudu • Uses ihe.net as the domain • acme1.ihe.net • Will also provide DNS service to get to the outside world (www.cnn.com)

8. SMTP Server • IP: • Only for systems using SMTP as part of a Connectathon test. • Please do not try to use this for your corporate email and ask for support. Corporate email is your own responsibility.

9. RIS Mall • IP: • It has these main functions: • Register a new patient. Send HL7 V2 ADT to one system (can repeat the send step as often as you like). • Create HL7 V2 Orders. • Supply DICOM Modality Worklist for modalities.

10. HIMSS Registration System • IP: • To be used for HIMSS demonstration and XDS, PIX/PDQ testing. • Register a new patient. It then sends HL7 V2 ADT messages to many destinations. These include • Patient Demographic Suppliers • PIX Managers • Anyone who wants an ADT feed • Useful for PIX testing among multiple participants

11. NIST Registry • IP: • Bill Majurski’s tool that will accept XDS.a / XDS.b submissions and assist with grading.

12. Syslog Proxy • IP: • Another NIST tool • You send syslog messages to this proxy. It will broadcast to other Audit Record Repositories. • It also provides some analysis of audit messages.

13. XDS Proxy • IP: • Another NIST tool. • Optional for 2009. • You send XDS messages to this proxy. It will capture messages and forward to XDS Registry / Repositories.

14. HL7 V2 Proxy • IP: • Provided by INRIA • Optional use for NA 2009 • Proxy will have one input TCP/IP port for each HL7 V2 receiver. • Any message sent to the proxy is sent to the corresponding participant. • Message is also captured and passed through a validation service to check for proper structure • Messages also available through Kudu web interface for review.

15. V2 V3 Gateway • IP: • Neither the RIS Mall nor HIMSS registration produce HL7 V3 messages. • This tool takes an HL7 V2 input ADT feed, translates to an HL7 V3 message and sends that message to a destination. • This is your mechanism to get HL7 V3 ADT information from the IHE management.

16. Gazelle Test Engine • IP: • Provided by INRIA • Optional use for NA 2009 • This is a prototype of the Gazelle Test Engine that we hope to use in production during the next year. • It replaces the Test Management in Kudu. • We will find some willing volunteers and ask them to spend some time with us using the Test Engine to run a few tests.

17. DICOM Central Archive • IP: • A DICOM Storage SCP with Query/Retrieve SCP. • This device is used in several Connectathon tests. • It is the location to store samples of your DICOM Objects for others to retrieve.

18. CPI Calibration Tools • IP: None • We will provide tools for calibrating screens (LCDs, CRTs) and plain film. • You need to bring a device for calibrating paper prints.

19. Certificate Management • IHE has not defined a structure for managing certificates. • We publish self-signed certificates in Kudu. • You need to load your partners’ certificates in your system. • There is no revocation.

20. IHE Tools Are Not Test Partners • Connectathon rules require testing with three test partners (for each test). • The systems listed here are not test partners. • For example, sending a document to a NIST Repository or registering a document with a NIST registry will not count as a test that we grade.

21. What is Missing From This Presentation • This is an overview of services and not the “how to” manual. • You need a separate presentation that tells you: • If I need to accomplish task X, what tools do I use and how do I use them?