NA 2009 Connectathon Support

21
NA 2009 Connectathon Support Description of Services Provided for Connectathon Participants

description

NA 2009 Connectathon Support. Description of Services Provided for Connectathon Participants. Connectathon Uses Private IP Space. Computers Inside Connectathon – Private Address Space. Router / Firewall / NAT. Internet. Private Address Space. Each computer receives a private address - PowerPoint PPT Presentation

Transcript of NA 2009 Connectathon Support

Page 1: NA 2009 Connectathon Support

NA 2009 Connectathon Support

Description of Services Provided for Connectathon Participants

Page 2: NA 2009 Connectathon Support

Connectathon Uses Private IP Space

Computers Inside Connectathon – Private Address

Space

Internet

Page 3: NA 2009 Connectathon Support

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

Page 4: NA 2009 Connectathon Support

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

This would be you.

Tools provided by NIST that are part of the test apparatus. Separate color for proper credit.

Page 5: NA 2009 Connectathon Support

These Systems are at the Connectathon

Kudu

HL7 V2 Proxy

RIS Mall

DICOM Central Archive

HIMSS Registration

V2 –> V3 Gateway

Participant 1

Participant 2

Gazelle Test

Engine

DNS Server

SMTP Server

Syslog Proxy

NIST Registry

XDS Proxy

CPI Calibration

Tools

Page 6: NA 2009 Connectathon Support

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

Page 7: NA 2009 Connectathon Support

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)

Page 8: NA 2009 Connectathon Support

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.

Page 9: NA 2009 Connectathon Support

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.

Page 10: NA 2009 Connectathon Support

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

Page 11: NA 2009 Connectathon Support

NIST Registry

• IP:• Bill Majurski’s tool that will accept XDS.a /

XDS.b submissions and assist with grading.

Page 12: NA 2009 Connectathon Support

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.

Page 13: NA 2009 Connectathon Support

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.

Page 14: NA 2009 Connectathon Support

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.

Page 15: NA 2009 Connectathon Support

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.

Page 16: NA 2009 Connectathon Support

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.

Page 17: NA 2009 Connectathon Support

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.

Page 18: NA 2009 Connectathon Support

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.

Page 19: NA 2009 Connectathon Support

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.

Page 20: NA 2009 Connectathon Support

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.

Page 21: NA 2009 Connectathon Support

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?