NA Connectathon 2020 Week Resources

  Bookmark this page for easy access to resources used to support your Connectathon testing.

Testing schedule for the week


Mon, Jan 20, 2020  8:00 am -  4:00 pm EST On-site check-in / badge pickup
Mon, Jan 20, 2020  8:00 am - 10:00 am Connectathon Participant system set-up
Mon, Jan 20, 2020 10:00 am -  5:30 pm Connectathon Test Session 1
Tue, Jan 21, 2020  9:00 am -  5:30 pm Connectathon Test Session 2
Wed, Jan 22, 2020  9:00 am -  5:30 pm Connectathon Test Session 3
Thu, Jan 23, 2020  9:00 am -  5:30 pm Connectathon Test Sesson 4
Fri, Jan 24, 2020  8:00 am -  noon Connectathon Test Session 5: Hard stop at noon


After-hours access:

Participants with a valid badge will have access to the Connectathon Floor. There is a curfew time TBD.

Daily 'need to know' announcements

The Connectathon venue makes oral announcements impractical.

Please check your email at 9am and 1:30pm each day. We will send twice-daily "need to know" announcements to the na_connectathon email list.

Seating Assignments

-- Seating assignments - There are two tabs in this spreadsheet. On the first tab, each cell represents one table with two chairs; table locations are identified by a letter/number, eg L28. The second tab shows seating assignments sorted by Organization. You can use the spreadsheet now for a table location if you need to ship something or order services. Your table location will also be entered in Gazelle before the end of the calendar year (2018). This will show up for you and your partners as you are running tests.

Network Info

Wireless / General

    • SSID:  NA2020
    • Password:  cleveland20

Wireless / PCD Testers

  • SSID:  PCD
  • Password:  provided on site

Gazelle Test Management

Gazelle on-site:

Outside of Connectathon floor, URL remains the same:

Guidance for Monday's session

We hope you've already reviewed the 10 Connectathon Tips from the Pros.

Monday 8:00-10am is for system set-up.  After 10am, we expect you to perform testing. Here is guidance on goals to accomplish during Monday's testing session:

    • Configure and connect to tools for your profiles.
    • Complete the 5-minute Consistent Time "CT_Client" test
    • Content Creators -- submit CDA/C-CDA docs into the samples area of gazelle for evaluation
    • Modalities/Evidence Creators -- submit DICOM samples into gazelle and the Central Archive
    • Submit media you create to the assigned Monitor -->  give XDM and PDI media to monitor Samantha Neiheisel at table M28.
      • It is good practice to hand a monitor your media rather than just dropping it at the table.
    • Any other tests labeled "*_Do_This_First" or "*_Read_This_First"
    • In general, work on other no-peer tests.
    • Then, move on to peer-to-peer tests.

Ask questions. Get help:

IHE USA staff - Help desk

      • logistics, "I'm lost", shipping...

Network staff - (Separate table, just inside the balllroom)

Tool help - see section below

Dr. Phil - (C31)

      • First & last resource for technical support.  Ask me anything.
        • If I do not know, I will find someone who does.
      • Gazelle help. Traditional Level 1 and Level 2 support.
        • e.g. "I need to reset my password"
      • Monitor support

Steve Moore - (K31)

      • QRPH, PCC and C-CDA tests, test requirements & grading => support for participants and monitors.
      • "I need to drop a profile/actor in QRPH or PCC"

Lynn Felhofer - (L28)

      • ITI and Radiology tests, test requirements & grading => support for participants and monitors
      • "I need to drop a profile/actor in RAD or ITI"

Anne-Gaëlle / Malo Toudic - (C28)

      • Gazelle support. This is Level 3 support.

Paul Sherman - (H28)

      • PCD tests, test requirements & grading => support for participants and monitors
      • "I need to drop a profile/actor in PCD"

Assigned partners and assigned patients

For Document Sharing (XD*, XC*, MHD) profiles and ATNA, Connectathon Managers make some assignments to help manage testing.  First-time participants can read an overview of multiple affinity domains at Connectathons here. This section only applies to test systems in those profiles.

See Lynn Felhofer (L28) with any questions about these assignments.

Tools - configuration, location & support


Gazelle Test Management

Support Malo (C28)
Summary Overall test management during Connectathon.  
Provider Organization Kereval (IHE Europe) 
Gazelle Proxy

Proxy is accessible at

Support  Malo (C28)
Summary Captures messages exchanged between two test systems and enables message validation.  Applicable to messaging in all IHE profiles that do not require TLS communication.  When participants link proxy message in test instances, monitors can use the link to examine message content and (for some messages) call validators in EVSClient.
Provider Organization Kereval (IHE Europe) 
Gazelle Security Suite (GSS)
Support Malo (C28) 

Source of digital certificates for ATNA/TLS.

Simulates an Audit Record Repository (syslog collector).

Validates syslog audit records.

TLS Simulators (client & server), including for new ATNA options.

Home of the ‘ATNA Questionnaire’ for systems testing ATNA.

SAML assertion provider for XUA.

Provider Organization Kereval (IHE Europe)
Gazelle EVSClient
Support Malo (C28)
Summary Validators for HL7v2, v3 messages, CDA documents, & FHIR Resources. Multiple DICOM validators. Other validators: XDW, PDF/A, DSUB, HPD… When you validate a message from within the Gazelle Proxy or Gazelle Samples area, it calls validators within the EVSClient.
Documentation User Manual
Provider Organization Kereval (IHE Europe), with embedded validators provided by many organizations
Gazelle Patient Manager
Support Anne-Gaëlle (C28)
Summary Simulators for actors in PAM, PDQ*, PIX* are used by participants during pre-Connectathon testing; sometimes during Connectathon.  Source of test patients during Connectathon.   
Connectathon tests *do not* call for monitors to use Patient Manager.  
Documentation User Manual
Provider Organization Kereval (IHE Europe)
Gazelle Order Manager
Support Anne-Gaëlle (C28)

Order Placer and Order Filler simulator in departmental workflow profiles; DICOM Modality Worklist provider (SCP) and HL7 order exchange.

Simulators are used by participants in RAD and LAB during pre-Connectathon testing; sometimes at Connectathon, especially as a DICOM Modality worklist SCP

Provider organization

Kereval (IHE Europe)

PCD Tools  
Configuration http://pcdtool:8080/pcdtool
Support John (E7)
Summary Used in PCD profile testing to validate one to one messages passing patient and device information. New functionality validates some detailed ACM profile content.
Support Steve Moore(K31)
Summary Used to test C-CDA documents. Not for general CDA testing.
Provider Organization NIST
PIX/PDQ and Vital Records Test Tools
Support Jungyub (M26)
Summary Validators for PIXv2, PIXv2, PDQv2 and PDQv3 messages. Validation for Vital Records Death Reporting.

on-line tool documentation

Provider organization


CDA Validation Tools
Support Steve (K31)

For PCC, QRPH, and C-CDA testing


IHE CDA Testing Procedure Overview

XDS Toolkit

See details on the homepage for XDS and FHIR toolkit:

>> On the Connectathon floor:   http://nist1:8080/

>> From outside:


Bill (J31)

Sunil (J32)

Summary Validates messages and simulates actors in document sharing profiles, eg XC*, XDS.  Specific tests contain instructions to use Toolkit to verify messages, or as a Doc Consumer simulator to perform queries against participants' tests systems.
Provider Organization NIST
XDS-I Tools
Configuration http://xds-imaging-tools:8080/toolkit
Support Steve (K31)
Summary For testing XDS-I and XCA-I implementations
Provider Organization NIST, + Mallinckrodt Institute of Radiology (for XDS-I & XCA-I)
FHIR Read-Write Server (HAPI)

Web GUI:

Server base URL (R4): http://fhir-read-write:8080/fhir/baseR4  

Server base URL (STU3):  http://fhir-read-write:8080/fhir/baseDstu3

Support Steve (K31)

(1) Hosts the Connectathon patients as FHIR Patient Resources. These Patient Resources will be referenced by other Resources that are created/exchanged in peer-to-peer tests .  i.e. you will not reference a copy of this resource that resides on your server or that of your test partner. 

(2) Hosts FHIR Resources that are test data for various IHE Profiles, e.g., mCDS, QEDm, MHD-SDC.

(3) Participants can upload & validate FHIR Resources created by their systems. 

-- -- Instructions are in Connectathon test '*_Resource_Check* for several profiles.

(4) Participants that are FHIR clients will upload a FHIR CapabilityStatement for their test system onto this server, making them available to all participants and monitors.  Instructions are in test '01_DoThis1st_CapabilityStatement'

Provider Organization

HAPI Server deployed at Connectathon by Mallinckrodt Institute of Radiology

FHIR Toolkit

See details on the homepage for XDS and FHIR toolkit:

>> On the Connectathon floor:   http://nist1:8080/

>> From outside:


Bill (J31)

Sunil (J32)


MHD profile testing

Documentation  Overview training recording
Provider Organization  NIST
DICOM Central Archive (dcm4chee)

GUI front-end: http://central-archive:8080/dcm4chee-arc/ui2

login/password: admin/admin (to add your AE title so the archive will accept your association)

IP addr / port:  /  11112

IP addr / port:  /  11112




Support Steve (K31)
Summary Used as a commonly-accessible repository for DICOM objects.   Participants store their objects here.  Available to other participants via DICOM C-FIND, C-MOVE, QIDO-RS, and WADO-RS.  Monitors use the web-based GUI to verify that participants have stored their objects here.
Provider organization
Mitre Canary

 GUI front-end: http://central-archive:18080

Note: This is correct. We are running the canary tool on the same host as the Central Archive.

Support Steve (K31)

Used to test VRDR/FHIR

Provider organization


Support Malo (C28)

SAML assertion provider - XUA and SeR testing

Provider Organization

Kereval (IHE Europe)

Index to IHE Test Tools:

NA Connectathon DNS


  1. We use a fake domain name ( for Connectathons in North America. Particpant systems are assigned more or more host names (e.g., acme2) and the fully qualified domain name (FQDN) for that host would be
  2. The Gazelle Test Management System ("Gazelle") is hosted at
  3. Some other tools such as the Gazelle Security Suite are hosted at
  4. The server also hosts other content such as documentation.
  5. Prior to the connectathon, these two systems live outside of the Connectathon test room and have public IP addresses:
  6. During the event:
    1. The full server lives in Cleveland on the private network used for testing.
    2. The tooling part of is brought to Cleveland and lives on the private network.
    3. Other content (documentation) remains on the original
  7. The Gazelle Test Management software records URL's that link to items inside the system or inside the system. The software works best if you use the fully qualified domain name in the URL rather than trying to use an IP address or just "gazelle"
  8. In previous years, we have seen evidence that DNS "stuff" from offsite locations such as your hotel might be cached in your system and interfere with your work in the testing area. We have advice below on how to manage that.

What Does This Mean for You?

Manual Network Configuration (i.e., Fixed IP Address)

  1. Make sure you set the Search Domain to:
    1. That means if someone tells you their hostname is acme2 and you try to connect to acme2, your underlying system software should try a DNS lookup on and things should just work.
  2. For DNS servers, use only the server we supply:
    1. If you use a different DNS server, you will not be able to resolve IP addresses for your partner systems.
    2. You will also get redirected to the public IP address of some of the resources listed above, and that will cause a (large) mess.

What Else Should You Do?

  1. After you connect to the Connectathon network, run the following (or equivalent) commands from a console window to determine the IP address of two systems. You should get the answer listed. If you do not get the answers listed, your DNS has a problem and needs to be fixed. You can see Phil DePalo if you need help
    1. nslookup (Answer:
    2. nslookup (Answer:
  2. When you return to your hotel room and decide you need to do more work, you can still connect to and/or Your hotel DNS should give you the public IP address of those systems at home, and you will be redirected to the Convention Center.
    1. When you are in the Convention Center and you use the public IP address for either of those resources, your connection goes out the firewal to the server at home and then gets redirected back through the firewall. The round trip traffic just puts more load on the network for no benefit.
  3. Repeat the first step above (nslookup) every morning when you connect to the Connectathon network. It might have worked on Monday but not on Tuesday.
  4. Resist the temptation to enter a fixed IP address when you browse to Gazelle Test Management ( or to the other tools at

What If?

  • You might have a link to documentation that starts with That should still work inside the Convention Center through redirects. If you have problems getting to such documentation, use this prefix: That URL points to the IHE Europe server back in Rennes and should not have any redirect issues.
    • Do not use this link for anything other than documentation.
    • Do not use this link for any tools